andrew wrote:
Barbara Duprey wrote:
I'd have thought that "VARCHAR" would automatically expand as needed
up to at least 255, but it doesn't, and the field definitions cannot
be modified in place. The option is presented to delete the field and
append a new one as redefined, but that discards all the data. (Issue
2).
That was a problem with versions of OOo up to 2.2.1. In the current
2.3 developers build you can enlarge the size of a varchar field, in
place.
Also - in the earlier versions you can do it also, but not using the
GUI table editor. You must use an actual SQL DDL ALTER TABLE ALTER
COLUMN command from the SQL window.
The syntax for that command can be found in the HSQLdb Users Manual,
and that document can be found at http://hslqdb.org
Ah, yes. I'd still prefer this to be done automatically when the data
exceeded the field capacity, perhaps after verification that this is
what's wanted, but I'm glad the new version will at least allow the
redefinition without data destruction or programmerese. (In my former
life, I was a programmer in IBM's Federal Systems Division for thirty
years, but SQL was never a language I needed more than a nodding
acquaintance with. Lots of others, but not that!) Anyway, Issue 2 is
officially declared dead. Thanks for the pointer to the documentation -
though I suspect there's a typo, right?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
