Hi Andrew, > 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?
Yes. I didn't consider this a really useful feature. Even if it were, it would probably be very confusing. Finally, the target audience for the feature is *not* the database guy knowing what VARCHAR/LONGCARCHAR means, but the people which would be alienated by those words ... > Also, regarding quoting. HSQLDB supports not only the textdb.all_quoted > property but also the textdb.quoted property. > ... > 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? "quoted=false" means you cannot insert quoted strings - hmm, how would this look to the user? (Currently, HSQL even shreds the data file in some scenarios, when this option is set, which indicates it really isn't widely used.) Yes, there might be existing files which contain unescaped quotes, but couldn't we agree that those need pre-processing? I'm reluctant here, also because adding both options would add additional (not strictly necessary, IMO) complexity to the UI. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
