Eigenbase JIRA  History | Log In     Get help!  
Issue Details [XML]

Key: LDB-167
Type: Bug
Status: Closed
Resolution: Won't Fix
Priority: Major
Assignee: Sunny Choi
Reporter: Sunny Choi
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
LucidDB

flatfile adapter text delimiter weirdness

Created: 12/Sep/07 05:02 PM   Updated: 12/Sep/07 05:02 PM
Component/s: Flatfile
Affects Version/s: None
Fix Version/s: None


 Description   
[migrated jira issue from LER-3974]

for numeric columns, flatfile adapter will complain about empty values being non-numeric if they're quoted.

that is, the empty sequence (field delimiter)(field delimiter), such as:

\t\t

...is considered numeric enough for flatfile wrapper not to complain.

but, with text delimiters, the likewise empty sequence (field delimiter)(text delimiter)(text delimiter)(field delimiter), such as:

\t""\t

...is not numeric and wrapper will choke.

On may think that "text delimiter" would imply a text value and thus the error being perfectly understandable, but since we do quote non-empty numeric values such as "4711", this is sort of inconsistent.

 All   Comments   Change History      Sort Order:
Comment by Sunny Choi [12/Sep/07 05:02 PM]
There is no inconsistency. Note the following sentence in http://www.eigenbase.org/wiki/index.php/LucidDbFlatFileWrapper

> Note that empty quotes ("") represents the empty string, while a completely empty value () represents a null.

And null is a legal numeric value, whereas empty string is not (according to the rules for CAST, which is what we use to arbitrate the interpretation of flatfile values).

In that document, I have added a link to this bug as clarification.