Le 23/10/2012 07:38, David Smith a écrit :
Hi David,
Strange.. It said it was completed successfully. When I do this, I
can now see the ID column and it appears I can add records. However,
when I go into the design view for the table, there is no ID column or
primary key columns and it shows only the columns I had before. It
also throws an error when I try to put in any records. "Attempt to
insert null into non-nullable column "?". But I don't have any
columns labeled "?".
Did you restart LO (and reload the ODB file) each time you made a
structural change ?
Also, there is a problem with adding auto-incrementing fields using
the design view. It just doesn't allow you to do it if the
auto-incrementing field isn't the first field in the table. With your
SQL, I now see an auto-incrementing field at the end of the table
which is pretty nice, and something I was trying to do earlier.
If the behaviour you describe above is reproducible, that would be a
bug. There shouldn't be AFAIK a requirement for the first field to be an
autoincrementing primary key in hsqldb.
Should I be filing bug reports?
IMHO, yes. At least someone else can then test, confirm/deny.
Alex
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
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
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.