Recent changes to bugs

#136 Improper handling of tables with spaces in their names

Mike — Tue, 13 Jun 2017 18:02:47 -0000

Additional info... using the MySql export option.

Improper handling of tables with spaces in their names

Mike — Tue, 13 Jun 2017 18:01:46 -0000

Using version: mdbtools-0.7.1-3.el7.x86_64 under CentOS 7

The scripts: mdb-schema and mdb-export do not properly handle table names with spaces in them, specifically in the IF EXISTS DROP lines in mdb-schema, and in the INSERT lines created in mdb-export. It appears any data for a table with a space in the name will not be exported.

debug.c:488: missing NULL sentinel

dcb — Tue, 01 Apr 2014 08:03:16 -0000

debug.c:488:41: warning: missing sentinel in function call [-Wsentinel]

Source code is

    gchar *str2 = g_strconcat(str, " None");

Suggest new code

    gchar *str2 = g_strconcat(str, " None", NULL);

mdb-export does not escape column names

James Cranch — Thu, 27 Jun 2013 13:42:32 -0000

I was trying to export a table whose column names -- rather annoyingly -- contain commas. The output CSV does not have inverted commas around those column names, and thus CSV readers interpret it as multiple column names.

I am using mdbtools as it is in Debian stable (wheezy) right now; Debian identifies it as version 0.7-1.

All numeric fields exported in scientific notation

Casey — Thu, 01 Nov 2012 16:43:31 -0000

All numeric fields are being exported in scientific notation.

mdb-schema with -N option shouldn't qualify constraint names

Daniel Schüssler — Mon, 03 Sep 2012 21:05:51 -0000

Example output line of `mdb-schema -N somenamespace foo.mde postgres`:

ALTER TABLE "somenamespace"."bar" ADD CONSTRAINT "somenamespace"."baz" FOREIGN KEY ...

Qualified constraint names are invalid in postgres (at least - haven't checked with other RDBMSs).

mdb-export returns no rows (just column names)

Matthew Kidd — Thu, 05 Apr 2012 06:21:38 -0000

When I run 'mdb-export -Q filename ReceivedData' on the attached JET 3 format file, it returns the column names but no rows even though the table shows 660 rows when opened in Microsoft Access 2003. I see this problem both on the current mdbtools package for Ubuntu and after building the CVS checkout as of today. I also made the change noted in Bug Id 2912667 and recompiled but this did not solve the problem.

mdb-export returns no rows (just column names)

Matthew Kidd — Thu, 05 Apr 2012 05:11:13 -0000

build fails at compile time beacuse of glib

rude_boy — Thu, 15 Mar 2012 09:49:29 -0000

Hi,

./autogen output ends with:
(...)
checking for iconv declaration...
extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking Are we using flex ... yes
./configure: line 11896: syntax error near unexpected token `2.0.0'
./configure: line 11896: `AM_PATH_GLIB_2_0(2.0.0)'

I use ubuntu oneiric desktop.

Please update the manpage

Simon Eugster — Mon, 14 Nov 2011 13:34:43 -0000

Quote from the mdb-schema manpage:
backend
Specifies target DDL dialect. Supported values are access, sybase, oracle, and postgres.
So I re-wrote the schema manually to MySQL. Then I went to your site and saw that you also support MySQL, so I tried mysql as backend and it worked mostly!