HI,
Another couple of questions from looking at the initial spec.
Section 1.3.2 Line Settings
HSQLDB supports separate separators for VARCHAR and LONGVARCHAR fields.
It does not appear that the 'Edit Linked Table' dialog has any support
for this. Is this a decision then to not offer this via the GUI and
leave it for 'advanced users' via the textdb.lvs property?
Also, regarding quoting. HSQLDB supports not only the textdb.all_quoted
property but also the textdb.quoted property. Here is an excerpt from
the users manual - Chapter 6
When the default options all_quoted= false and quoted=true are in
force, fields that are written to a line of the csv file will be
quoted only if they contain the separator or the quote character. The
quote character is doubled when used inside a string. When
all_quoted=false and quoted=false the quote character is not doubled.
With this option, it is not possible to insert any string containing
the separator into the table, as it would become impossible to
distinguish from a separator. While reading an existing data source
file, the program treats each individual field separately. It
determines that a field is quoted only if the first character is the
quote character. It interprets the rest of the field on this basis.
I don't see any support for this on the 'Edit Linked Table' dialog mock up.
At first I thought, no problem this is all about bringing data into the
database. But that's not true, this is not part of an import
specification. Once the text table is created via this feature the users
are free to write to it also, so would it would seem to make sense to
support both properties?
Sincerely,
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
