https://bugs.documentfoundation.org/show_bug.cgi?id=100167
--- Comment #9 from [email protected] ---
Thanks for your help.
Although I agree that the lack of a PK causes certain problems when
querying/updating/deleting, a PK should not be a requirement and the db should
still work - at least to the extent that one record can be distinguished from
others... or at least give an error message if it is to be "required".
It shouldn't be necessary to add a PK in order to be able to view and edit a
table, within certain constraints (no unique value so duplicate rows are
vulnerable) but a "quick and dirty" implementation in this way should be
possible.
"SELECT ic.issue, ic.cat,catdescr FROM issue_cat ic, cat WHERE ic.cat=cat.cat"
...works in MariaDB (and Access) where issue_cat has no PK.
If this, however, is an underlying requirement of HSQLDB, is there some kind of
error condition that can be detected and a message displayed to let the user
know what the problem is? The current situation doesn't seem ideal.
Thanks for your help.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
