[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mdbtools-dev
Subject:    RE: [mdb-dev] Segfault when listing tables andproblemsexportingtables
From:       "Fergus Allan" <f_W_allan () yahoo ! co ! uk>
Date:       2004-06-15 22:22:29
Message-ID: 003301c45327$3fc8f120$10282052 () local20
[Download RAW message or body]


As a design point, table names should only be case sensitive when
delimited

Thus:

Select * from tbl_Neo
Select * from TBL_NEO

Are identical, but 


Select * from "tbl_Neo"
Select * from "TBL_NEO"

Are different. Example assumes double quote is the delimiter character.

Regards

Fergus Allan



-----Original Message-----
From: mdbtools-dev-admin@lists.sourceforge.net
[mailto:mdbtools-dev-admin@lists.sourceforge.net] On Behalf Of David
Mansfield
Sent: 14 June 2004 22:06
To: Matt Reynolds
Cc: MDB Tools List
Subject: Re: [mdb-dev] Segfault when listing tables
andproblemsexportingtables

On Mon, 2004-06-14 at 16:06, Matt Reynolds wrote:
> On Mon, 2004-06-14 at 12:35, David Mansfield wrote:
> > On Mon, 2004-06-14 at 14:58, Matt Reynolds wrote:
> > /usr/local/mdbtools/bin/mdb-export 05260930_orlando.mdb \
> > 	QcpCdma1xActiveSetInfo_XXX
> > 
> 
> Actually, I think I lied.  This does work, but isn't the table I want
to
> dump.
> 
> This command:
> mdb-export 05260930_orlando.mdb \ QcpCDMA1xRadioLinkProtocolStats_XXX
> 
> Still doesn't output anything.
> 
> So, looking into it a bit more, I realized that mdb-tables isn't
dumping
> the table I'm interested in.  It shows :
> QcpCdma1xRevPwrCtrl_XXX_FltStats QcpCdma1xRadioLinkProtocolStats
> QcpCdma1xRadioLinkProtocolStats_ QcpCdma1xRadioLinkProtocolStats_
> QcpCdma1xRadioLinkProtocolStats_
> 
> Those last three tables are supposed to be :
> QcpCdma1xRadioLinkProtocolStats_XXX
> QcpCdma1xRadioLinkProtocolStats_XXX_IntBest
> QcpCdma1xRadioLinkProtocolStats_XXX_UI4$I2
> 
> I think that's why I can't dump them.  Any idea why these tables
aren't
> being dumped?

Hmm. You're right.  There's something really funky going on.  If  you
look closely at the output of mdb-tables, or mdb-schema, there are some
'unprintable' characters being generated as part of the table name for
some tables, including these.

So the table name is not being extracted correctly.  That's probably a
bug somewhere...  Possibly in the unicode string extraction or
something.

Let's see... Ok.  It seems as though the 'hardcoded' max object name
length of 30 is screwing you up.  If we hardcode it to 50 it works. 
(begs a different question but....).  So try the attached patch on top
of the combined patch and it seems to work.

NOTE: the table names ARE case sensitive, so be sure to use mdb-tables
to get the exact name, then cut-and-paste for mdb-export.

David




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
mdbtools-dev mailing list
mdbtools-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mdbtools-dev
[prev in list] [next in list] [prev in thread] [next in thread]