<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FIREBIRD: incorrect ASC order with varchar data" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124054#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FIREBIRD: incorrect ASC order with varchar data" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124054">bug 124054</a> from <a class="email" href="mailto:woodford@pobox.com" title="Tim <woodford@pobox.com>"> Tim</a> <pre>(In reply to Robert Großkopf from <a href="show_bug.cgi?id=124054#c25">comment #25</a>) > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>