Icon View Thread

The following is the text of the current message along with any replies.
Messages 21 to 24 of 24 total
Thread IMPORT with QUOTE CHAR #0
Fri, Jan 15 2010 2:42 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Malcolm,

<< Then I simply edited the key value to avoid an index error, and:

IMPORT TABLE "ATest"
FROM "Vladimir.txt"
IN STORE "DRBackup"
DELIMITER CHAR #124
QUOTE CHAR #0;

All the text column values starting with a non-ascii char(code point) are
imported as NULLs. >>

Please send me the database catalog and the import file that you're using.

<< It seems EDB import just can't cope with unquoted text. >>

No, that is certainly not the case.  More than likely it is something weird
with a #0 character causing some functionality to think that the string is
terminated.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jan 15 2010 4:25 PMPermanent Link

"Malcolm"
Tim Young +AFs-Elevate Software+AF0- wrote:

+AD4- Malcolm,
+AD4-
+AD4- Please send me the database catalog and the import file that
you're
+AD4- using.
+AD4-

Stuff sent.

--
Sat, Jan 30 2010 5:47 PMPermanent Link

"Malcolm"
Malcolm wrote:

+AD4- Stuff sent.

I confirm that build 8 has resolved the issue.

Thanks a lot .. feeling guilty at asking for the feature which I
initially thought would be a mere trifle for you.  Surprised

--
Mon, Feb 1 2010 10:57 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Malcolm,

<< I confirm that build 8 has resolved the issue. >>

Thanks.

<< Thanks a lot .. feeling guilty at asking for the feature which I
initially thought would be a mere trifle for you.  Surprised >>

Yeah, but it resulted in this last bug being found and fixed, and it didn't
have anything to do with the #0 quote char, so it was a good thing. Smiley

--
Tim Young
Elevate Software
www.elevatesoft.com

« Previous PagePage 3 of 3
Jump to Page:  1 2 3
Image