Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.16
-
None
-
Windows Server 2012
Description
When you attempt to create a CONNECT DBF table, the create command executes without error. However when an attempt is made to query the data, an LRECL error is thrown and no data is returned.
I have also attempted to manually set the LRECL via the options in the create statement but the same result is achieved. I have verified the DBF file and it opens fine it is a DBF version III file.
The following executes fine:
create table dbf_demo engine=CONNECT table_type=DBF file_name='C:/MariaDB 10.1/data/demo/test_dbf.dbf'; |
However the following:
select * from dbf_demo; |
throws this error:
SQL Error (1296): Got error 174 'Table/File lrecl mismatch (857,301)' from CONNECT |
Upon further inspection the DBF file is actually being read and the table is being created but you cannot use SELECT to view even the empty columns in the table, it consistently throws the LRECL error.
If you run the following:
show create table dbf_demo |
You can then see the structure of dbf_demo(FIELD NAMES CHANGED):
CREATE TABLE `dbf_demo` ( |
`FIRST_NAME` char(49) NOT NULL, |
`LAST_NAME` char(10) NOT NULL, |
`EVENT_DATE` char(10) NOT NULL, |
`EVENT_TYPE` char(2) NOT NULL, |
`GRID` char(13) NOT NULL, |
`LONG` double(11,2) NOT NULL, |
`LAT` double(11,2) NOT NULL, |
`LOCATION` char(181) NOT NULL, |
`APPROVED` char(13) NOT NULL |
) ENGINE=CONNECT DEFAULT CHARSET=utf8 `TABLE_TYPE`='DBF' `FILE_NAME`='C:/MariaDB 10.1/data/demo/test_dbf.dbf' `LRECL`=310 |
Attachments
Activity
This error seems to occurs only on a limited number of platforms. I could not reproduce it and I checked on builbot where MariaDB is compiled on many platforms and all the tests implying DBF tables pass.
Therefore I cannot currently fix it but here is what I did:
When you create a DBF table with the option accept set to true, for instance adding:
option_list='Accept=1'
|
the mismatch between the calculated LRECL and the one extracted from the DBF file header is no more regarded as an error but just as a warning. In addition, because I don't know whether the LRECL is miscalculated or lost between the time it is computed and the time it is compared, I have added a trace showing the calculated value. This trace can be activated by:
set connect_xtrace=1
|
Then the LRECL is set to the value extracted from the DBF file header.
I don't know whether will actually fix your problem (there can be other side effects) so I'd like you to test it in the next MariaDB release and let me know what happens.
Thanks, Olivier.
I'll keep you informed, I see that the changes will be inserted in 10.1.19.
Greetings, Marco.
As a matter of facts, this solution was buggy and could cause a server crash because the block size has to be updated with the new LRECL.
This is fixed now but this will be available only in next versions of MariaDB.
Hi, Olivier.
Just tested the 10.1.22 win64, now it does work.
Thanks, Marco.
Hi, Olivier. I attach a second test case (untouched, no anonymization), it has the same behaviour
Error:
Errore SQL (1296): Got error 174 'Table/File lrecl mismatch (463,155)' from CONNECT
Table created with:
create table testdbf2 ENGINE=CONNECT table_type=DBF file_name='(omissis)/test_dbf_2.dbf';
Resulting create table code:
CREATE TABLE `testdbf2` (
`CODICE` CHAR(2) NOT NULL,
`NOME` CHAR(30) NOT NULL,
`NOME1` CHAR(30) NOT NULL,
`NOME2` CHAR(30) NOT NULL,
`PRESENTE` CHAR(1) NOT NULL,
`TURNISTA` CHAR(1) NOT NULL,
`ORA_INIZIO` CHAR(8) NOT NULL,
`CAMBIO_T` CHAR(5) NOT NULL,
`CAMBIO_T2` CHAR(5) NOT NULL,
`MATT_DALLE` CHAR(5) NOT NULL,
`MATT_ALLE` CHAR(5) NOT NULL,
`POME_DALLE` CHAR(5) NOT NULL,
`POME_ALLE` CHAR(5) NOT NULL,
`NOTT_DALLE` CHAR(5) NOT NULL,
`NOTT_ALLE` CHAR(5) NOT NULL,
`MINUTI_D` CHAR(4) NOT NULL,
`MINUTI_U` CHAR(5) NOT NULL,
`MANSIONE` CHAR(1) NOT NULL,
`LIBERO` CHAR(1) NOT NULL,
`IMPIAN_OP` CHAR(1) NOT NULL
)
COLLATE='utf8_general_ci'
ENGINE=CONNECT;
Debian Wheezy,64bit mariadb 10.1.17 64bit