. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. The Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Protecting User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2.2. Limiting the distribution of data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . 24 3. Data Types and Subtypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.1. Integer Data Types . . . Floating-Point Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.2.1. Approximate Floating-Point Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.3. Fixed-Point Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . 22 3. Data Types and Subtypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.1. Integer Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.2. Floating-Point Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3. Fixed-Point Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7. Protecting your data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . this by prepending xnet:// to the database path or alias, but on POSIX, you’re stuck. The only solution there is to connect to a regular database through the server, for example using localhost:employee access to a database file can copy it, install it on a system under their own control, and extract all data from it — including possibly sensitive information. Anybody who has filesystem-level write access

true = NULL • NULL and NULL = NULL In version 2.5 and earlier, Firebird SQL doesn’t have a boolean data type; nor are true and false existing constants. In the leftmost column of the explanatory table trigger language). 5.3.1. EXISTS EXISTS tells you whether a subquery 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 such a situation those rare NULL cases may go unnoticed for a long time, silently corrupting your data. 9.2. CASE expression Firebird introduced the CASE construct in version 1.5, with two syntactic

Firebird version) • /opt/firebird for Linux and other Unix systems. The gsec utility manipulates data in the table(s) in the security database, and by doing so, allows users to be added, amended and trying to use the IPCServer transport implemented in Firebird 1.5 which doesn’t work on Vista. The solution is to use TCP local loopback. • Put an alias in aliases.conf for the path to your security.fdb still exists in Firebird 2.5. C:\>gsec -z gsec version WI-V1.5.0.4306 Firebird 1.5 GSEC> The solution is to have a small file containing the command quit and force gsec to read this file when it needs

Note in V.2.1 Metadata Need to be Upgraded If your databases contain text BLOBs storing non-ASCII data then the backup/restore cycle is not enough to upgrade them to ODS 11.1. Please pay attention to the (V.2.1) Malformed UTF8 strings and text blobs are no longer allowed. This affects not just user data but also the metadata stored in the system tables. There is a metadata script to enable you to upgrade allow Firebird to use indexes. Indexes Involving Data Type Coercion May Be Ignored (V.2.1) In cases where an indexed field and an argument have different data types and the implicit conversion cannot be performed

how you can make InterBase and Firebird 1.5 coexist on your Windows computer. Please note that the solution provided here will not allow InterBase and Firebird to run at the same time. You can toggle between

transformées » en chaînes vides. Ce n'est pas vraiment juste, mais c'est considéré comme la moins mauvaise solution: dans l'ancienne situation , les chaînes valides (mais vides) étaient sans merci ramenées à NULL

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. Data Page — Type 0x05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8.2. Record Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4. Examining The Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 8.4.1. Compressed Data. . . . . . . . . .