Am 21.04.2012 18:58, Mark Stanton wrote:
Copying the structure and data in one go, as offered by the import
wizard, never creates any auto-ID fields.
Would this be a sensible improvement to make?
Mark Stanton
One small step for mankind...
Hello Mark,
Yes, it would be useful to have more import options that actually work
when importing a pseudo-database (mostly spreadsheet lists) into a true
database or into HSQLDB at least:
[X] Use first column as column name
[X] Create primary key [Name Box]
[ ] Create primary key as auto-ID
And another exclusive option:
[o] Use existing column <list box> as auto-ID
[ ] Use existing column(s) <multi-select list box> as primary key
When importing from a true database into another true database, these
options should be preset according to the situation in the source table
but still modifyable. Sometimes you want to import with no constraints
at all.
My above statement
... never creates any auto-ID fields.
is not entirely correct. At least a copy&paste between 2 HSQLDBs creates
the integer PK as auto-ID. It creates an exact copy of the table. Some
level of detection seems to be implemented already.
Copying from HSQLDB to H2 (a similar Java DB) does creates an integer PK
but not as an auto-ID field.
I think it can be very hard to implement for all types of connectable
database engines. There are UNO interfaces to detect the capabilities
and idiosyncrasies of some database driver. May be this can be utilized,
may be not.
--
For unsubscribe instructions e-mail to: [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
