4 2.1. Generic response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. SQL response . . . . . . . . 2.3. Fetch response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4. Slice response . . . . . . deferring the read of the response. Chapter 1. Introduction 3 Chapter 2. Responses The wire protocol has a limited set of responses. Some operations have a specific response, which is described together

309 8.1. Context Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 8.1.1. RDB$GET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 8.1.2. RDB$SET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 9. Context Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

database files and in particular access to the metadata stored in those files. It has been written in response to frequent questions on the Firebird lists concerning these issues. The article avoids technical the embedded server, the server operates in the application (and therefore the user’s) security context. This means that the embedded server will only be able to access database files that the user could

410 8.1. Context Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 8.1.1. RDB$GET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 8.1.2. RDB$SET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 11. Context Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 18.2. Response Codes Are Usually Zero. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . encountered. Always check the response code returned by gfix to be sure that it worked. However, see the caveats section below for details because it looks like the response code is always zero — at least transaction -object my_employee is in use linux> echo $? 0  As with many failures of gfix, the response code returned to the operating system is zero. Under Firebird 2, the error message is more self-explanatory:

.......................... 406 RDB$GET_CONTEXT ........................................................................................... 406 RDB$SET_CONTEXT ....................................... ....................................................................................... 692 MON$CONTEXT_VARIABLES ...................................................................................... Краткий синтаксис: CREATE DOMAIN [AS] [DEFAULT { | | NULL | <context_var>}] [NOT NULL] [CHECK ()] [COLLATE collation]; См. также:

OCTET_LENGTH() OVERLAY() PI() 8 Руководство по языку SQL POSITION() POWER() RAND() RDB$GET_CONTEXT() RDB$SET_CONTEXT() REPLACE() REVERSE() RIGHT() ROUND() RPAD() SIGN() SIN() SINH() SQRT() SUBSTRING() TAN() [COLUMN] colname SET DEFAULT 83 Руководство по языку SQL ::= literal-value | context-variable | NULL Пример: ALTER TABLE CUSTOMERS ALTER ENTEREDBY SET DEFAULT CURRENT_USER Совет APP_NAME, SERVER_PID, PC_PID, DATE_START_CONNECT) VALUES ( CURRENT_USER, CURRENT_CONNECTION, RDB$GET_CONTEXT('SYSTEM', 'CLIENT_ADDRESS'), :REMOTE_PROTOCOL, :APP_NAME, :SERVER_PID, :PC_USER_PID, CURRENT_TIMESTAMP);

398 8.1.1. RDB$GET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 8.1.2. RDB$SET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678 MON$CONTEXT_VARIABLES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . erstellt. Kurzschreibweise CREATE DOMAIN name [AS] [DEFAULT { | | NULL | <context_var>}] [NOT NULL] [CHECK ()] [COLLATE ] Siehe auch CREATE DOMAIN im Abschnitt

expected %s at offset %ld, encountered %ld -104 335544425 ctxinuse Context already in use (BLR error) -104 335544426 ctxnotdef Context not defined (BLR error) -104 335544429 badparnum Bad parameter number dsql_blob_err Column is not a BLOB -206 335544596 dsql_subselect_err Subselect illegal in this context -206 336397208 dsql_line_col_error At line %d, column %d -206 336397209 dsql_unknown_pos At unknown dsql_cursor_not_found Cursor %s is not found in the current context -502 336003092 dsql_cursor_exists Cursor %s already exists in the current context -502 336003093 dsql_cursor_rel_ambiguous Relation %s is

expected @1 at offset @2, encountered @3 -104 335544425 ctxinuse Context already in use (BLR error) -104 335544426 ctxnotdef Context not defined (BLR error) -104 335544429 badparnum Bad parameter number dsql_blob_err Column is not a BLOB -206 335544596 dsql_subselect_err Subselect illegal in this context -206 336397208 dsql_line_col_error At line @1, column @2 -206 336397209 dsql_unknown_pos At unknown dsql_cursor_not_found Cursor @1 is not found in the current context -502 336003092 dsql_cursor_exists Cursor @1 already exists in the current context -502 336003093 dsql_cursor_rel_ambiguous Relation @1 is