https://bugs.documentfoundation.org/show_bug.cgi?id=124054
Alex Thurgood <ipla...@tuta.io> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEEDINFO
--- Comment #16 from Alex Thurgood <ipla...@tuta.io> ---
The real question to be answered, which may or may not be a bug, is that
either:
- the Firebird migration assistant ignores any previously set collation with
the existing hsqldb table and sets a default collation which doesn't allow
sorting in the way people expect with hsqldb ;
or
- if no default collation was set with the existing hsqldb table, then the
Firebird default collation sort behaviour is applied.
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.
Currently, with the limited information Tim has provided, there is no way of
telling where the problem lies.
@Tim: as has been requested many times, we need a representative hsqldb ODB
file that displays the behaviour you describe so that we can examine whether it
is indeed the migration assistant that is not working correctly, or whether it
is just down to a difference in the way Firebird behaves compared to hsqldb in
the absence of any specified collation.
--
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
