[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 --- Comment #30 from Robert Großkopf --- Isn't this one a feature request? There should be executed ALTER CHARACTER SET UTF8 SET DEFAULT COLLATION UNICODE directly after a new Firebird database has been created. Have forgotten this in last project and have to execute the SQL-code, copy and paste the tables and reconnect the relationships. Nothing for a "normal user". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 Robert Großkopf changed: What|Removed |Added Blocks||154426 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154426 [Bug 154426] [META] Steps to work with Base without needing Java -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 --- Comment #29 from bugreport...@protonmail.com --- Tools/SQL ALTER CHARACTER SET UTF8 SET DEFAULT COLLATION UNICODE changes the collation for new tables to UNICODE, but not for existing tables. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 --- Comment #28 from bugreport...@protonmail.com --- (In reply to Alex Thurgood from comment #16) > As the default behaviour under Firebird is different to hsqldb, the way to > workaround this is to: > > - either set the collation at the Query level escaping the built-in SQL > parser (run in direct SQL mode); > > - or ALTER the table definition to add the required collation. @Alex Thurgood comment 16-18 Please tell me the exact SQL command to alter the table definition for the whole odb file or one complete table in it to UNICODE ASC collation via Tools/SQL. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 --- Comment #27 from Tim --- (In reply to Robert Großkopf from comment #25) > The order of characters is Firebird-specific. I have changed the title for > this. > > Note: Has nothing to do with migration, it is the default behaviour of a new > created database in LO 6.3.0.0.beta1: > > Create a new database > Create a table with ID - INTEGER (primrary key), "Name" - VARCHAR > Input some data: > 1 Aaa > 2 Ba > 3 Za > 4 ab > 5 ca > > This data will be sorted by a query: > SELECT "Name" ORDER BY "Name" ASC > It will be shown the same way as sorted above: Capital letters first. > SELECT "Name" ORDER BY "Name" COLLATE UNICODE ASC > It will only work in direct SQL, so unusable for input data. But it will > order "Name" as the order will be in HSQLDB: > Aaa > ab > Ba > ca > Za > > I could confirm this buggy behaviour with LO 6.3.0.0.beta1 on OpenSUSE 15, > 64bit rpm Linux with a new created Firebird database. Still the same behavior with LO 6.4.1.2 under MACOS with a new created Base File using embeded Firebird. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6262 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 Robert Großkopf changed: What|Removed |Added OS|Mac OS X (All) |All -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 Xisco Faulí changed: What|Removed |Added Blocks||51780 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=51780 [Bug 51780] [META] Default to Firebird not HSQLDB in Base (for _new_ files) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 --- Comment #26 from Robert Großkopf --- (In reply to Robert Großkopf from comment #25) > This data will be sorted by a query: > SELECT "Name" FROM "Table" ORDER BY "Name" ASC > It will be shown the same way as sorted above: Capital letters first. > SELECT "Name" FROM "Table" ORDER BY "Name" COLLATE UNICODE ASC Wrong queries - corrected. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124054] FIREBIRD: incorrect ASC order with varchar data
https://bugs.documentfoundation.org/show_bug.cgi?id=124054 Robert Großkopf changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|Base - incorrect ASC order |FIREBIRD: incorrect ASC |in Form with varchar data |order with varchar data |containing accented | |characters | --- Comment #25 from Robert Großkopf --- The order of characters is Firebird-specific. I have changed the title for this. Note: Has nothing to do with migration, it is the default behaviour of a new created database in LO 6.3.0.0.beta1: Create a new database Create a table with ID - INTEGER (primrary key), "Name" - VARCHAR Input some data: 1 Aaa 2 Ba 3 Za 4 ab 5 ca This data will be sorted by a query: SELECT "Name" ORDER BY "Name" ASC It will be shown the same way as sorted above: Capital letters first. SELECT "Name" ORDER BY "Name" COLLATE UNICODE ASC It will only work in direct SQL, so unusable for input data. But it will order "Name" as the order will be in HSQLDB: Aaa ab Ba ca Za I could confirm this buggy behaviour with LO 6.3.0.0.beta1 on OpenSUSE 15, 64bit rpm Linux with a new created Firebird database. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
