https://bugs.documentfoundation.org/show_bug.cgi?id=124054
--- Comment #40 from Robert Großkopf <[email protected]> --- Please: This all has nothing to do with the reason for the order in Firebird. It has something to do what a user expect when he starts a form with many rows of data and will sort this data to get data he want. And the user expects it the way HSQLDB, MariaDB and PostgreSQL, all with drivers from LO, will sort. If this is sorted 'a' in front of 'A' or after 'A' isn't the problem. But 'a' after 'Z' is a horror. Example: I have a table for invoice codes - international published, only this table should be used. I try to order this table by the name of the code. Find "A Wheeled pallet with raised rim (81 x 72 x 135)" at row 4. Find "Wooden pallet 40 cm x 80 cm" at row 490. Find "access line" at row 491. The whole table has 2161 rows. Lower cased letter start at row 491. And now argue with ASCII and computer science. When trying this I didn't get anybody, who will use this kind of sorting in his database and all people will ask me: "Why can't you create the database in HSQLDB? It isn't usable for me this way." -- You are receiving this mail because: You are the assignee for the bug.
