https://bugs.documentfoundation.org/show_bug.cgi?id=147730
Robert Großkopf <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #10 from Robert Großkopf <[email protected]> --- I have tested this: Opened the table and switch to last row. Won't get all rows then, only some of the rows which contain an empty string as combined primary key. Opened a query and let me show the primary keys. If the query isn't editable (only one key) it will show all rows (141). If the query is editable, it will need pressing "last row" two times to switch to a wrong rows count (like 135 or something else). Base will set empty fields to NULL, and this seems to be the problem for the GUI. I would never use such a table for input new data, but you could list this data when switching to direct SQL and it works. You could also use direct SQL (or macros) to input new data. It is a bug to show the wrong number of rows, but I don't know how to handle this without throwing away all the features, which will work with NULL for an empty field. I would prefer to open a table write protected, if a primary key contains an empty string. Tested with OpenSUSE 15.3 64bit rpm Linux and LO 7.3.1.2 -- You are receiving this mail because: You are the assignee for the bug.
