Case-insensitive collation, works without taking character case into account. Added in Firebird 2.1 UNICODE_CI_AI Case-insensitive, accent-insensitive collation, works alphabetically without taking character case or accentuation of characters (similar to COLLATE PXW_CYRL). ... ORDER BY NAME COLLATE UNICODE_CI_AI 3.5.5. Character Indexes In Firebird earlier than version 2.0, a problem can occur with building not applied. Example CREATE TABLE TTT ( S VARCHAR (40) CHARACTER SET UTF8 COLLATE UNICODE_CI_AI ); COMMIT; SELECT CAST ('I have many friends' AS TYPE OF COLUMN TTT.S) FROM RDB$DATABASE; Conversions

Case-insensitive collation, works without taking character case into account. Added in Firebird 2.1 UNICODE_CI_AI Case-insensitive, accent-insensitive collation, works alphabetically without taking character case or accentuation of characters (similar to COLLATE PXW_CYRL). ... ORDER BY NAME COLLATE UNICODE_CI_AI Chapter 3. Data Types and Subtypes 46 3.5.5. Character Indexes In Firebird earlier than version not applied. Example CREATE TABLE TTT ( S VARCHAR (40) CHARACTER SET UTF8 COLLATE UNICODE_CI_AI ); Chapter 3. Data Types and Subtypes 58 COMMIT; SELECT CAST ('I have many friends' AS TYPE OF

2.1: • Тип данных SQL_NULL • Набор символов GB18030, алиас для WIN_1258 • Сортировка UNICODE_CI_AI для UTF8, сортировка GB18030 для GB18030 Язык определения данных (DDL) Изменения начиная с Firebird insensitive — ci), акцентно нечувствительными / диакритически чувствительными (accent insensitive — ai) или словарно отсортированными (dictionary-sorted - dic). Обратите внимание на то, что для новых наборов Chinese 2.5 GBK GBK_UNICODE Chinese 2.1 ISO8859_1 ES_ES_CI_AI Spanish ci, ai 2.0 FR_FR_CI_AI French ci, ai 2.1 PT_BR Brazilian Portuguese ci, ai 2.0 ISO8859_2 CS_CZ Czech 1.0 ISO_HUN Hungarian 1.5

(алфавитная). Пример: a, A, a, b, B... UTF-8 Сортировка происходит без учёта регистра символа. UNICODE_CI_AI Сортировка происходит без учёта регистра символа, в алфавитном порядке. Пример сортировки строк для UTF8 без учёта регистра символов (эквивалент COLLATE PXW_CYRL) ORDER BY NAME COLLATE UNICODE_CI_AI Типы данных 40 Индексирование символьных типов При построении индекса применяются. Примеры: CREATE TABLE TTT ( S VARCHAR (40) CHARACTER SET UTF8 COLLATE UNICODE_CI_AI); COMMIT; /* У меня много друзей (шведский)*/ SELECT Типы данных 50 CAST ('Jag har manga vanner'

mots clés begin...end autour des groupes de lignes. Je ne l'ai pas fait ici - je voulais écrire un faible nombre de lignes. Mais du coup j'ai compensé en ajoutant cette note ;-) Vérifier que des champs pas la brillante idée d'inverser l'expression et de l'utiliser comme un test d'inégalité (comme je l'ai déjà fait dans le passé): /* Ne faites pas cela! */ if (not(A = B or A is null and B is null)) then

funktioniert ohne Berücksichtigung der Groß-/Kleinschreibung. Hinzugefügt in Firebird 2.1 UNICODE_CI_AI Groß-/Kleinschreibung, akzentunabhängige Sortierung, arbeitet alphabetisch ohne Berücksichtigung von der Akzentuierung von Zeichen (ähnlich wie COLLATE PXW_CYRL). ... ORDER BY NAME COLLATE UNICODE_CI_AI 3.5.5. Zeichenindizes In Firebird vor Version 2.0 kann ein Problem beim Erstellen eines Indexes für angewendet. Beispiel CREATE TABLE TTT ( S VARCHAR (40) CHARACTER SET UTF8 COLLATE UNICODE_CI_AI ); COMMIT; SELECT CAST ('I have many friends' AS TYPE OF COLUMN TTT.S) FROM RDB$DATABASE; Konvertierungen

........................................................................................... 8 Performance .............................................................................................. executing the view's trigger code and again executing the table's trigger code. This situation caused performance problems or exceptions, particularly if blobs were involved. Now, if you define triggers for a if the backup subsequently turns out to be unrestorable. Performance The following changes should be noted as possible sources of performance loss: Existence Predicates NOT IN and ALL May Be Slow Firebird

allocated to store (cache) database pages in memory to help improve the efficiency of the database performance. It is far quicker to read data from memory that it is to have to physically read the data from  Please don’t consider page buffers value as an ultimate parameter to improve Firebird’s performance, and don’t set it too high without clear understanding what are you doing. The setting applies page becoming completely empty, then it can be used for any purpose within the database. • The performance of the database may be affected while the sweep is in progress.  Theoretically, it is possible

sup- port. Better performance in case of a small number of multiple connections that do not influence each other. No SMP support. On multi-processor Windows ma- chines, performance can even drop dramatically overwhelming), just pick one or the other. In most circumstances, chances are that you won't notice a performance differ- ence. Besides, you can always switch to the other architecture later; your applications configuration is forced writes off (or disabled). It is sometimes resorted to in order to improve performance during large batch operations. The big warning here is: do not disable forced writes on a Windows

multi-processor) sup- port. Better performance in case of a small number of connections that do not influ- ence each other. No SMP support. On multi-processor Win- dows machines, performance can even drop dramatically events with a firewall or tunnel). In most circumstances, chances are that you won't notice a performance difference. Note that you can always switch to the other architecture later; your applications configuration is forced writes off (or disabled). It is sometimes resorted to in order to improve performance during large batch operations. Disabling forced writes on Windows The big warning here is: do