. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 18.18. SET SQL DIALECT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 19.20. SHOW SQL DIALECT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -r2 role (uses quoted identifier) -s(qldialect) <dialect> SQL dialect (set sql dialect) -t(erminator) command terminator (set term) -tr(usted)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 9. Setting The Database Dialect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . set SQL role name -r(ollback) rollback transaction -sq(l_dialect) set database dialect n -sw(eep) force garbage collection -sh(utdown) shutdown read/write file system regardless of whether only SELECT statements are run or not.  Only databases in dialect 3 can be changed to read only mode. The command to set the required mode for a database is: gfix

ESQL nor ISQL flavours are described here unless mentioned explicitly. 2.1.2. SQL Dialects SQL dialect is a term that defines the specific features of the SQL language that are available when Chapter Three dialects are available: • Dialect 1 is intended solely to allow backward comptibility with legacy databases from very old InterBase versions, v.5 and below. Dialect 1 databases retain certain language language features that differ from Dialect 3, the default for Firebird databases. ◦ Date and time information are stored in a DATE data type. A TIMESTAMP data type is also available, that is identical

ESQL nor ISQL flavours are described here unless mentioned explicitly. 2.1.2. SQL Dialects SQL dialect is a term that defines the specific features of the SQL language that are available when Chapter Three dialects are available: • Dialect 1 is intended solely to allow backward comptibility with legacy databases from very old InterBase versions, v.5 and below. Dialect 1 databases retain certain language language features that differ from Dialect 3, the default for Firebird databases. ◦ Date and time information are stored in a DATE data type. A TIMESTAMP data type is also available, that is identical

Attempt to fetch past the last record in a record stream 0 335741039 gfix_opt_SQL_dialect -sql_dialect set database dialect n 0 335544875 bad_debug_format Bad debug info format -84 335544554 nonsql_security_rel 18 changed from DOUBLE PRECISION in SQL dialect 1 to 64-bit scaled integer in SQL dialect 3 -104 336003077 sql_db_dialect_dtype_unsupport Database SQL dialect @1 does not support reference to @2 datatype DATE must be changed to TIMESTAMP Firebird 2.1 Error Codes -104 335544796 sql_dialect_datatype_unsupport Client SQL dialect @1 does not support reference to @2 datatype -104 335544798 depend_on_uncommitted_rel

two SQL “dialects”: dialect 1 and dialect 3. New databases should always be created with dialect 3, which is more powerful in a number of respects. Dialect 1 is a compatibility dialect, to be used only Generator Basics 4 under InterBase 5.6 or earlier. One of the differences between the two is that dialect 1 has no native 64-bit integer type available. NUMERIC(18) columns for instance are stored internally biggest integer type in dialect 1 is the 32-bit INTEGER. In dialect 1 as in dialect 3, generators are 64-bit. But if you assign the generated values to an INTEGER column in a dialect 1 database, they are

Attempt to fetch past the last record in a record stream 0 335741039 gfix_opt_SQL_dialect -sql_dialect set database dialect n -84 335544554 nonsql_security_rel Table/procedure has non-SQL security class 18 changed from DOUBLE PRECISION in SQL dialect 1 to 64-bit scaled integer in SQL dialect 3 -104 336003077 sql_db_dialect_dtype_unsupport Database SQL dialect %d does not support reference to %s datatype 335544764 transitional_date DATE must be changed to TIMESTAMP -104 335544796 sql_dialect_datatype_unsupport Client SQL dialect %d does not support reference to %s datatype -104 335544798 depend_on_uncommitted_rel

335544764 transitional_date DATE must be changed to TIMESTAMP -104 335544796 sql_dialect_datatype_unsupport Client SQL dialect does not support reference to datatype -104 335544798 depe 18 changed from DOUBLE PRECISION in SQL dialect 1 to 64-bit scaled integer in SQL dialect 3 -104 336003077 sql_db_dialect_dtype_unsupport Database SQL dialect does not support reference to 335544765 read_only_database Attempted update on read-only database -817 335544766 must_be_dialect_2_and_up SQL dialect is not supported in this database -817 335544793 ddl_not_allowed_by_db_sql_dial

перед выполнением оператора создания базы данных задать нужный диалект, выполнив оператор SET SQL DIALECT. По умолчанию база данных создаётся в 3 диалекте. Кто может создать базу данных? Выполнить оператор База данных будет в 1 диалекте, и использовать набор символов по умолчанию WIN1251. SET SQL DIALECT 1; CREATE DATABASE 'D:\test.fdb' USER wizard PASSWORD 'player' ROLE RDB$ADMIN DEFAULT CHARACTER SET используемая операционная система или пока не будет исчерпана память на внешнем носителе. SET SQL DIALECT 3; CREATE DATABASE 'baseserver:D:\test.fdb' USER wizard PASSWORD 'player' ROLE 'RDB$ADMIN' PAGE_SIZE

entwickelte Datenbanken und Anwendungen wird die Verwendung von Chapter 2. SQL Sprachstruktur 18 Dialect 3 dringend empfohlen. Sowohl Datenbank- als auch Verbindungsdialekte sollten übereinstimmen, außer außer unter Migrationsbedingungen mit Dialekt 2. Diese Referenz beschreibt die Semantik von SQL Dialect 3, sofern nicht anders angegeben. 2.1.3. Fehlerbedingungen Die Verarbeitung jeder SQL-Anweisung (CUST_NO) ) 3.1.3. BIGINT BIGINT ist ein SQL:99-kompatibler 64-Bit-Integer-Datentyp, der nur in Dialect 3 verfügbar ist. Wenn ein Client Dialekt 1 verwendet, wird der vom Server gesendete Generatorwert