Bug Hunting Session
Bug 116935 - Firebird: Support for collation in the UI
Summary: Firebird: Support for collation in the UI
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.0.3.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Database-Firebird-Default
  Show dependency treegraph
 
Reported: 2018-04-11 09:19 UTC by Gerhard Schaber
Modified: 2019-05-27 08:26 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerhard Schaber 2018-04-11 09:19:28 UTC
It would be great to have support for UNICODE_CI and/or UNICODE_CI_AI collation for CHAR and VARCHAR fields in the UI. The character set UTF8 must be set automatically for those fields. For for new databases the global default character set is UTF8, now, anyway, if I am not mistaken. The collation could be provided as list to select from, or generally offered as VARCHAR_IGNORECASE field type, if that makes sense. I do not know the exact differences between a VARCHAR_IGNORECASE field in HSQLDB and a VARCHAR field with UNICODE_CI_AI or UNICODE_CI collation in Firebird.
Comment 1 Alex Thurgood 2018-04-12 06:56:05 UTC
Seems like a reasonable request. Confirming.
Comment 2 Gerhard Schaber 2018-04-12 08:20:25 UTC
As reference, this is a sample statement that creates a table with a case and accent insensitive field:

CREATE TABLE "testcollation" (
  "ID" INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH 0) NOT NULL PRIMARY KEY, "name" VARCHAR(50) CHARACTER SET UTF8 COLLATE UNICODE_CI_AI
)

Then insert entries with upper and lower case characters

You will ten be able to query for all records case insensitively.
select * from "testcollation" where "name" = 'whatever'