. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.8.1. Input and output parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 7.1.1. DML Statements with Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 RDB$PROCEDURE_PARAMETERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 6.8.2. Input and output parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 7.1.1. DML Statements with Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733 RDB$PROCEDURE_PARAMETERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.5. Describe bind (input parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 8.7. Set default blob parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . id (0) String Database path or alias Buffer Database parameter buffer Table 1. Example of parameters sent in the DPB Parameter Description Value Optional isc_dpb_version1 Version (must be first

CONNECT [USER username] [PASSWORD password] [ROLE role_name]; If any of the parameters to the connect command contains spaces, you must wrap that parameter in single or double quotes transaction parameters. Durability ensures that once a transaction commits, its updates survive within the database, even if there is a subsequent system crash. There are several parameters available ensure consistency within the database. These parameters invoke the concept of concurrency. To ensure data integrity, there are four configurable parameters affecting concurrency: isolation level; lock

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Gsplit Command Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . we will discuss the following: • Command line options for gsplit. • Gsplit options and their parameters. • Splitting backups using gsplit. • Joining backup chunks using gsplit.  From Interbase 6 although, strictly speaking, the -help option isn’t really valid. These are: -split_bk_file <parameters> Specifies that gsplit is to be used to split the output from gbak into a number of different

............................................................................. 7 Configuration Parameters .............................................................................................. Firebird simultaneously. Change to API DPB Parameters in V.2.1.2 and V.2.0.5: IMPORTANT A long-standing, legacy loophole in the handling of DPB parameters enabled ordinary users to make con- nection settings change makes it possible to specify queries like SELECT * FROM TAB ORDER BY 5. Configuration Parameters Configuration parameter DeadThreadsCollection is deprecated The parameter DeadThreadsCollection

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 RDB$PROCEDURE_PARAMETERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . die Abfrage jedoch zwei separate und unabhängige _Parameter. Der Server kann den Typ des zweiten Parameters nicht bestimmen, da er mit IS NULL verknüpft ist. Der Datentyp SQL_NULL löst dieses Problem. Untertypen 45 Nach dem Aufruf von isc_dsql_describe_bind() wird der SQLTYPE des zweiten und vierten Parameters auf SQL_NULL gesetzt. Firebird hat keine Kenntnis von ihrer speziellen Beziehung zum ersten und

all the gfix commands have the same format when typed on the command line: gfix [commands and parameters] database_name The commands and their options are described in the following sections. The database -⁠pa[ssword], or -⁠tru[sted]. Optionally combined with -⁠role. These can be supplied for every command as parameters on the commandline, or can be configured once in a pair of environment variables. -? This switch database on a remote server, you will always be required to pass the -⁠u[ser] and -⁠pa[ssword] parameters. Chapter 3. Gfix Commands 6 Chapter 4. Shadow Files A shadow file is an additional copy of

bytes. Only SYSDBA and co-admins can use all these commands. Ordinary users can change their own parameters (such as password, name parts and tags, but not active/inactive) using ALTER USER name or ALTER security-related configuration parameters. You can significantly enhance your system’s security if you raise the protection level wherever possible. This is not only a matter of setting parameters, by the way: other The first line defines the alias (see next item), and everything between the curly brackets are parameters for that specific database. You’ll find databases.conf in the same directory as firebird.conf

........................................................................... 672 RDB$PROCEDURE_PARAMETERS .................................................................................... 672 RDB$PROCEDURES поведение и сообщения о конфликте зависят от параметров транзакции, определённых в TPB (Transaction Parameters Block): Таблица 5.11. Влияние параметров TPB на явную блокировку Режим TPB Поведение isc_tpb_consistency isc_except, , isc_formatted_exception, , parameters>. Поскольку используется новый код ошибки (isc_formatted_exception), клиент должен быть версии