интегрированной среде, дающей возможности создания запросов к разным базам данных (cross-database query). Другая причина перехода - исключение привязки к определенному поставщику программного обеспече- поддержка этого API. Это также является базисом для компонент доступа сред разработки Delphi и C++ Builder, таких как InterBase Objects (IBO), FIBPlus, InterBase Express (IBX), UnifiedIB (UIB) и др. Переход Monitor InterBase Heartbeat (commercial) Profiler InterBase Observer SQL Profiler (commercial) Query Analyzer Planalyzer Утилита Server Network IBOConsole Service Manager Control Panel Applet Указанный

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 Using MON$STATEMENTS to Cancel a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 This Firebird SQL Language Reference is the first comprehensive manual to cover all aspects of the query language used by developers to communicate, through their applications, with the Firebird relational NULL After processing, at the API level, the query will look like this: WHERE col1 = ? OR ? IS NULL This is a case where the developer writes an SQL query and considers :param1 as though it were a variable

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760 Using MON$STATEMENTS to Cancel a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760 This Firebird 4.0 Language Reference is the third comprehensive manual to cover all aspects of the query language used by developers to communicate, through their applications, with the Firebird relational processing, at the API level, the query will look like this: Chapter 3. Data Types and Subtypes 56 WHERE col1 = ? OR ? IS NULL This is a case where the developer writes an SQL query and considers :param1 as

to a Firebird database. It accepts DSQL statements along with a group of SET and SHOW commands to query and interact with the Firebird database. Some SET commands can be incorporated in DDL scripts to terminated, using a QUIT or EXIT 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 on/off SET EXPLAIN -- toggle display of query access plan in the explained form SET HEADING -- toggle display of query column titles SET LIST -- toggle column

of the NULL in B. But if B is indexed, IN returns false and NOT IN returns true. As a result, the query select A from TA where A not in ( select B from TB ) returns a dataset with one record — containing FROM Farms WHERE EXISTS (SELECT * FROM Landowners WHERE Landowners.Name = Farms.Farmer) This query returns the names of all farmers who also figure in the Landowners table. The EXISTS predicate returns SELECT Farmer, Cows, Sheep FROM Farms WHERE Cows + Sheep > 0 On the surface, this looks like a query returning all the farms that have at least one cow and/or sheep (assuming that neither Cows nor Sheep

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.7. Rows affected by query execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 9.4. Query service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a prepare with the obtained statement handle. 5.4. Describe Describe of output parameters of a query is done using the statement information request message Example of requested information items •

Синтаксис: SELECT [FIRST ] [SKIP ] FROM ... ... , ::= integer literal | query parameter | (integer-expression) Таблица 5.1. Параметры предложений FIRST и SKIP Параметр Описание integer literal Целочисленный литерал. query parameter Параметр запроса. ? — в DSQL и :paramname — в PSQL. Операторы DML 243 Параметр Описание обозначенная псевдонимом таблицы и псевдонимами полей. Синтаксис: Операторы DML 252 (select-query) [[AS] derived-table-alias] [()] := column-alias

posting by Ann Harrison on the Firebird Support mailing list. The posting was in response to a query asking if there is a way to reduce the memory cache without giving up too much performance? This was thought to be the time required to load back all the cache pages from disc before the first query (after hibernation) could be processed. The cause was confirmed and the DBA responsible for the database disc. To inspect the current statistics for the database as a whole, we would use the following query in isql: tux> isql employee Database: employee SQL> SELECT MON$PAGE_READS, MON$PAGE_WRITES, MON$PAGE_FETCHES

Examples a) 1. When an alias is present it must be used or no alias at all must be used. This query was allowed in FB1.5 and earlier versions: SELECT RDB$RELATIONS.RDB$RELATION_NAME FROM RDB$RELATIONS rejected in Firebird 2.n, even though it was tolerated in InterBase and previous Firebird versions. Query Plans Stricter validation of user-specified plans User-specified plans are validated more strictly to perform a backup/restore cycle. Plan must refer to all tables in query Using a plan without a reference to all tables in query is now illegal and will cause an exception. Some previous versions would

appears more than once in USING clause -104 336397237 dsql_cte_not_used CTE "@1" is not used in query -105 335544702 like_escape_invalid Invalid ESCAPE sequence -105 335544789 extract_input_mismatch after isc_svc_query() -901 335740933 gfix_replay_req Replay log pathname required -901 336330757 gbak_switches_conflict Conflicting switches for backup/restore -901 336986117 fbsvcmgr_query_err Unknown Unknown tag (@1) in isc_svc_query() results -901 335544326 bad_dpb_form Unrecognized database parameter block -901 335740934 gfix_pgbuf_req Number of page buffers for cache required -901 336986118 fbsvcmgr_switch_unknown