<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Base - incorrect ASC order in Form with varchar data containing accented characters" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124054#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Base - incorrect ASC order in Form with varchar data containing accented characters" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124054">bug 124054</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>Reading <a class="bz_bug_link bz_status_NEW " title="NEW - Firebird: Support for collation in the UI" href="show_bug.cgi?id=116935">bug 116935</a>, I see that there is already a request for COLLATION options to be offered at the UI level... this implies that a DDL statement to create a collation at table/field level works. So, if it can't be shown that the migration assistant is faulty, e.g. for ignoring a default pre-set collation in hsqldb, or for setting an incongruous collation on migration, then the workaround is indeed to use the COLLATE statement when creating the table (or subsequently issue an ALTER TABLE statement to add it). If it can be shown that the migration assistant incorrectly assigns a new collation or ignores an existing collation, then we can confirm this bug report (with a modified title).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>