. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 3.4.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 3.4.4. Session Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.4.5. Time Zone Format. . . . . . 2 3.4.6. Operations Using Date and Time Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.4.7. Supplemental Time Zone Features . . . . . . . . . . .

.............................................................................................. 35 TIME ................................................................................................. TRANSACTION ............................................................................. 379 POST_EVENT ................................................................................................. .................................................................................... 390 CURRENT_TIME .................................................................................................

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.4.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.4.4. Operations Using Date and Time Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 7.6.17. POST_EVENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.4.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 7.7.21. POST_EVENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 11.4. CURRENT_TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Контекстные переменные CURRENT_CONNECTION 6 Руководство по языку SQL CURRENT_ROLE CURRENT_TIME CURRENT_TIMESTAMP CURRENT_TRANSACTION CURRENT_USER DELETING GDSCODE INSERTING NEW 'NOW' OLD BUFFER, CHECK_POINT_LENGTH, COMPILETIME, CONTINUE, DB_KEY, DEBUG, DESCRIBE, DISPLAY, ECHO, EDIT, EVENT, EXTERN, FOUND, GOTO, GROUP_COMMIT_, HELP, IMMEDIATE, INDICATOR, INIT, INPUT, ISQL, LC_MESSAGES, LC_TYPE SQLWARNING, STATIC, TERMINATOR, TRANSLATE, 14 Руководство по языку SQL TRANSLATION, VERSION, WAIT_TIME и WHENEVER. Дополнительно Изменения начиная с Firebird 2.1: • Шестнадцатеричные обозначения цифр

database file, and the users are able to continue processing data as normal and without loss. In the event that your main database file(s) become corrupted or unreadable, the DBA can activate Chapter 4. Shadow maintenance  The DBA can set up the database to automatically create a new shadow file in the event of a current shadow being activated. This allows a continuous supply of shadow files and prevents -⁠k[ill]. In the event that a database running with shadow files loses a shadow, or a shadow becomes unusable for some reason, the database will stop accepting new connections until such time as the DBA kills

outside the scope of the cursor loop was accepted by the PSQL parser, allowing the likelihood of run-time occurring as a result. Now, it will be rejected in the procedure or trigger definition. NULLS are STRING_ARGUMENT, index scanning is allowed because the conversion is deterministic. (V.2.1) Some date/time expressions in Dialect 1 can not benefit from available indices either, e.g., DATE_ FIELD > 'NOW' typedef void (*ISC_EVENT_CALLBACK) (void*, ISC_USHORT, const ISC_UCHAR*); ISC_STATUS isc_que_events( ISC_STATUS*, isc_db_handle*, ISC_LONG*, short, const ISC_SCHAR*, ISC_EVENT_CALLBACK, void*);

dyn_no_grant_admin_opt User %s has no grant admin option on SQL role %s -901 335544510 lock_timeout Lock time-out on wait transaction -901 336068798 dyn_user_not_role_member User %s is not a member of SQL role identifier_too_long BLR syntax error. Identifier %s... is too long -901 335544859 invalid_time_precision Time precision exceeds allowed range (0-%d) -901 336397211 dsql_too_many_values Too many values -902 335544724 net_event_connect_err Failed to establish a secondary connection for event processing. -902 335544725 net_event_listen_err Error while listening for an incoming event connection request

dyn_no_grant_admin_opt User @1 has no grant admin option on SQL role @2 -901 335544510 lock_timeout Lock time-out on wait transaction -901 336068798 dyn_user_not_role_member User @1 is not a member of SQL role identifier_too_long BLR syntax error. Identifier @1... is too long -901 335544859 invalid_time_precision Time precision exceeds allowed range (0-@1) -901 335544866 met_wrong_gtt_scope @1 cannot depend -902 335544724 net_event_connect_err Failed to establish a secondary connection for event processing. -902 335544725 net_event_listen_err Error while listening for an incoming event connection request

file(s) are updated and in this manner, the shadows are an identical copy of the database. In the event of a problem, the SYSDBA can manually activate a shadow, or have the Firebird engine activate one pag_generation Four bytes, unsigned. Bytes 0x04 - 0x07. The page generation number. Increments each time the page is written back to disc. pag_scn Four bytes, unsigned. Bytes 0x08 - 0x0b. Originally used is permitted. hdr_creation_date Eight bytes, signed. Bytes 0x2c - 0x33 on the page. The date and time (in Firebird’s own internal format) that the database was either originally created/rewritten or