firebird 40 language reference
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 8.1.1. RDB$GET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 8.12.3. RDB$GET_TRANSACTION_CN() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . named zone may change. • For TIME WITH TIME ZONE, calculating a time zone offset for a named zone to get the local time in the zone applies the rules valid at the 1st of January 2020 to ensure a stable value0 码力 | 778 页 | 3.43 MB | 1 年前3firebird language reference 30 rus
Функции для работы с контекстными переменными ................................................ 406 RDB$GET_CONTEXT .......................................................................................... Операторы DDL 148 FROM goods JOIN price ON goods.code_goods = price.code_goods LEFT JOIN sp_get_balance(goods.code_goods) b ON 1 = 1; Пример 4.64. Создание обновляемого представления Во время работы DDL триггера доступно пространство имён DDL_TRIGGER для использования в функции RDB$GET_CONTEXT. Его использование также допустимо в хранимых процедурах и функциях, вызванных триггерами DDL0 码力 | 719 页 | 3.98 MB | 1 年前3Firebird 2 QuickStart
....................................................................................... 29 How to get help ............................................................................................. Firebird version. This guide covers versions 2.0– 2.0.6 and 2.1–2.1.4. For all other Firebird versions, get the corresponding Quick Start Guide at http://www. firebirdsql.org/en/documentation/. Some warnings not even read-only. They query databases via the server, and the server makes sure that users only get the allowed type of access (if at all) to any objects within the database. Disable Classic local mode0 码力 | 40 页 | 218.42 KB | 1 年前3Firebird 2.5 Language Reference
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 8.1.1. RDB$GET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . date literals without a time part, as well as 'TODAY', 'YESTERDAY' and 'TOMORROW' automatically get a zero time part. If, for some reason, it is important to you to store a Dialect 1 timestamp literal It stores the time of day within the range from 00:00:00.0000 to 23:59:59.9999. If you need to get the time-part from DATE in Dialect 1, you can use the EXTRACT function. Examples Using EXTRACT()0 码力 | 521 页 | 2.30 MB | 1 年前3firebird 5 quickstartguide
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 8. How to get help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . matches your Firebird version. This document covers Firebird 5. For all other Firebird versions, get the corresponding Quick Start Guide at https://www.firebirdsql.org/en/documentation/. Chapter 1. CURRENT USER, which always refers to the user you are logged in as. If the command succeeds, you won’t get any feedback. Instead, isql will just print the next “SQL>”- Chapter 5. Server configuration and management0 码力 | 49 页 | 396.21 KB | 1 年前3Firebird 1.0 QuickStart
....................................................................................... 22 How to get help ............................................................................................. matches this guide. This guide covers versions 1.0, 1.0.2 and 1. 0.3. If you run Firebird 1.5 or higher, get the appropriate version of the Quick Start Guide at http://www.firebirdsql.org/manual/ (HTML) or http://www substituting this example IP address for the IP address that your server is broadcasting. Warning If you get a timeout message, study the Using Firebird manual – Chapter 6: Network Configuration, and Chapter0 码力 | 26 页 | 179.05 KB | 1 年前3firebird 30 sprachreferenz
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 8.1.1. RDB$GET_CONTEXT() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . quantity AS quantity FROM goods JOIN price ON goods.code_goods = price.code_goods LEFT JOIN sp_get_balance(goods.code_goods) b ON 1 = 1; Chapter 5. Anweisungen der Datendefinitionssprache (DDL) 154 start with SP_)'; set term !; create trigger trig_ddl_sp before CREATE PROCEDURE as begin if (rdb$get_context('DDL_TRIGGER', 'OBJECT_NAME') not starting 'SP_') then exception e_invalid_sp_name; end0 码力 | 701 页 | 3.12 MB | 1 年前3Firebird Generator Guide: A guide on how and when to use generators in Firebird
Firebird database. You can create one by giving it a name: CREATE GENERATOR GenTest; Then you can get its current value and increase or decrease it just like a “var i:integer” in Delphi, but it is not well as long as the values lie within the 32-bit range. But as soon as that range is exceeded, you get a numeric overflow error: dialect 3 is much stricter on range checking than dialect 1! 2.4.1. Client value, consider it as “gone forever”. When you start a transaction and then call a generator and get a value of — let’s say — 5, it will remain at that value even if you roll back the transaction (!)0 码力 | 20 页 | 169.00 KB | 1 年前3Firebird 2.5 LangRef Update Russian
NULLIF() 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() 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); в фиктивную переменную и тем самым выиграть во времени её выполнения. Примечание Функции RDB$GET_CONTEXT и RDB$SET_CONTEXT хотя и классифицированы в этом руководстве как внутренние, фактически0 码力 | 364 页 | 1.45 MB | 1 年前3Firebird Null Guide: NULL behaviour and pitfalls in Firebird SQL
mind as you read through the rest of the guide, and most of the seemingly illogical results you can get with NULL will practically explain themselves. A few sentences and examples in this guide were use of NULL literals is a sign of poor SQL design and will lead to NULL results where you meant to get true or false. In that sense the earlier, more restrictive policy was safer, although you could always returns at least one row of data. Suppose you want a list of farmers who are also landowners. You could get one like this: SELECT Farmer FROM Farms WHERE EXISTS (SELECT * FROM Landowners WHERE Landowners0 码力 | 69 页 | 479.63 KB | 1 年前3
共 27 条
- 1
- 2
- 3