🚀 go-pugleaf

Hi Mike,

Let me post small part from article (yet to be published soon):
=== (Migration from Paradox and dBase to Interbase / Firebird - Practical
Guide) ===
3) Secondary Indexes
Interbase has same indexes definition as Paradox/dBase with few exceptions:
- Index names should be unique across one Intrebase database. Same rule
applies for Paradox table only so you will have to check index names to
avoid duplication.
- Interbase support Case Sensitive indexes only. This is the one and the
only option for Interabase indexes.

If you need create case insensitive index you have two options:
a) Use case insensitive COLLATE clause order (see example):
  CREATE TABLE "TABLE" (
    "ID" INTEGER,
    "NAME" VARCHAR(50) CHARACTER SET ISO8859_1 COLLATE EN_US);

  CREATE INDEX "IND_TABLE_NAME" ON "TABLE" ("NAME");

Index "IND_TABLE_NAME" will be in fact case insensitive because of case
insensitive COLLATE EN_US used for field "NAME".

Following SQL will use "IND_TABLE_NAME" index and return case insensitive
result set:
  SELECT "NAME"
  FROM "TABLE_NAME"
  ORDER BY "NAME"

All SQL operations (comparison, ORDER BY and GROUP BY) on fields with case
insensitive COLLATE order will be also case insensitive by default.
You can overwrite COLLATE order for every comparison, ORDER BY and GROUP BY
operations but in this case index will not be used.

Following SQL will not use "IND_TABLE_NAME" index and return case sensitive
result set:
  SELECT "NAME"
  FROM "TABLE_NAME"
  ORDER BY "NAME" COLLATE ISO8859_1

Please remember about that drawback with COLLATE clause.
===
To be more specific collations like EN_US, DU_NL, FR_FR etc. seems to be
case insensitive so probably you can rely on naming convention but if you
can run some tests then it will be more obvious.

My best regards,
Alex