. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 6.8.2. Input and output parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANSITIONS returns the set of rules between the start and end timestamps for a named time zone. The input parameters are: • RDB$TIME_ZONE_NAME type CHAR(63) • RDB$FROM_TIMESTAMP type TIMESTAMP WITH TIME usage is not limited to column definitions for tables and views. Domains can be used to declare input and output parameters and variables in PSQL code. 3.11.1. Domain Attributes A domain definition

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.8.1. Input and output parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . usage is not limited to column definitions for tables and views. Domains can be used to declare input and output parameters and variables in PSQL code. 3.9.1. Domain Attributes A domain definition contains domain, its dependencies must be taken into account: whether there are table columns, any variables, input and/or output parameters with the type of this domain declared in the PSQL code. If you change domains

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 17.7. INput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . command. Isql can be used interactively to: ◦ Create, update, query, and drop data or metadata. ◦ Input a script file containing a batch of SQL statements in sequence without prompting. ◦ Add and modify -f(etch_password) fetch password from file -i(nput) input file (set input) -m(erge) merge standard error -m2 merge

‘=’ operator, just like assigning values. You can also include NULL in an insert list or use it as input parameter to a stored procedure (both are special types of assignments). if ( YourString = 'Dunno' is now passed if the condition resolves to NULL. Only an unambiguous false outcome will cause the input to be rejected. In practice, this means that checks like check ( value > 10000 ) check ( upper( between 30 and 36 ) check ( ColA <> ColB ) check ( Town not like 'Amst%' ) ...will reject NULL input in Firebird 1.5, but let it pass in Firebird 2. Existing database creation scripts will have to be

follows: tux> gbak -z gbak:gbak version LI-V2.5.0.26074 Firebird 2.5 gbak: ERROR:requires both input and output filenames gbak:Exiting before completion due to errors tux> echo $? 1 This displays the file name on the command line.  You may, if you wish, read the dump data directly from standard input rather than a backup file. In this case, you must specify stdin as the dump file name. You could a potentially large dump file. To do this, you pipe the output of a gbak backup directly to the input of a gbak restore, as follows. tux> # Clone a test database to the same server, without requiring

335544702 like_escape_invalid Invalid ESCAPE sequence -105 335544789 extract_input_mismatch Specified EXTRACT part does not exist in input datatype -150 335544360 read_only_rel Attempted update of read-only list -162 335544685 no_dbkey Dbkey not available for multi-table views -170 335544512 prcmismat Input parameter mismatch for procedure %s -170 335544619 extern_func_err External functions cannot have gbak_filename_missing Requires both input and output filenames -901 335544331 bad_tpb_form Invalid format for transaction parameter block -901 336330763 gbak_dup_inout_names Input and output have the same name

335544702 like_escape_invalid Invalid ESCAPE sequence -105 335544789 extract_input_mismatch Specified EXTRACT part does not exist in input datatype -150 335544360 read_only_rel Attempted update of read-only table list -162 335544685 no_dbkey Dbkey not available for multi-table views -170 335544512 prcmismat Input parameter mismatch for procedure @1 -170 335544619 extern_func_err External functions cannot have Requires both input and output filenames -901 335544331 bad_tpb_form Invalid format for transaction parameter block Firebird 2.1 Error Codes -901 336330763 gbak_dup_inout_names Input and output have

335544702 like_escape_invalid Invalid ESCAPE sequence -105 335544789 extract_input_mismatch Specified EXTRACT part does not exist in input datatype -150 335544360 read_only_rel Attempted update of read-only table gfix_trn_not_valid Transaction state not in valid range. -901 335741012 gfix_unexp_eoi Unexpected end of input -901 335741018 gfix_recon_fail Failed to reconnect to a transaction in database -901 335741036 destinations specified -901 336330762 gbak_filename_missing Requires both input and output filenames -901 336330763 gbak_dup_inout_names Input and output have the same name. Disallowed. -901 336330764 gbak_inv_page_size

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.5. Describe bind (input parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . isc_info_sql_scale • isc_info_sql_field • isc_info_sql_relation 5.5. Describe bind (input parameters) Describe of input parameters of a query is done using the statement information request message Example statement has input parameters: Buffer Parameters in BLR format Int32 Message number (0) ?? Int32 Number of messages (1) ?? Buffer Parameter values If not statement has no input parameters: Buffer

Объявление в базе данных BLOB фильтра. Доступно в: DSQL, ESQL. Синтаксис: DECLARE FILTER filtername INPUT_TYPE OUTPUT_TYPE ENTRY_POINT 'function_name' MODULE_NAME 'library_name'; фильтра с уже существующими комбинациями входных и выходных типов BLOB приведёт к ошибке. Предложение INPUT_TYPE идентифицирует тип преобразуемого объекта (подтип BLOB). Предложение OUTPUT_TYPE идентифицирует Пример 4.115. Создание BLOB фильтра с использованием номеров подтипов DECLARE FILTER DESC_FILTER INPUT_TYPE 1 OUTPUT_TYPE -4 ENTRY_POINT 'desc_filter' MODULE_NAME 'FILTERLIB'; Пример