https://bugs.documentfoundation.org/show_bug.cgi?id=124054
Robert Großkopf <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW --- Comment #32 from Robert Großkopf <[email protected]> --- (In reply to Mike Kaganski from comment #31) > So, we still don't have a single HSQLDB file with a wanted collation, which > we could try converting to Firebird to see how the conversion changes the > collation in the result? > > This one needs a sample - let me stress it again: a sample HSQLDB embedded > file. This has nothing to do with converting from HSQLDB to Firebird. HSQLDB will order the entries right way. It will always set the collation to local settings of your LO system, here for example to SET DATABASE COLLATION "German" It is the default of Firebird, which doesn't work well. For internal Firebird it would work to set the collation when creating a new database as described. It has to be collation UNICODE: ALTER CHARACTER SET UTF8 SET DEFAULT COLLATION UNICODE will give the right behavior. But we could also try to set collation by reading the local settings. But another bug will appear at this moment when you try to set the collation and export internal database to an external database: https://bugs.documentfoundation.org/show_bug.cgi?id=159155 -- You are receiving this mail because: You are the assignee for the bug.
