. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.2. Testing for NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.4. Testing DISTINCTness (Firebird 2+) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 17. Testing for NULL and equality in practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 17.1. Testing for NULL — if it matters

............................................................................................ 11 Testing your installation .............................................................................. you will be directed to them at a certain point during your reading of the Installation Notes. Testing your installation If everything works as designed, the Firebird server process will be running on the installation. It will also start up automatically whenever you restart your computer. Before testing the Firebird server itself, it is advisable to verify if the server machine is reachable from the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.4. Testing your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bird-1.5.6-ReleaseNotes.pdf# page=96 3.4. Testing your installation If you want to connect to your Firebird server across a network, then before testing the Firebird server itself, you may want to case, you will only see a firebird process if a client connection has been made. Another way of testing the server after installation is by starting a Firebird client (e.g. /opt/firebird/bin/isql) and

program ...................................................................................... 7 Testing your installation .............................................................................. you to modify the scripts and make some manual adjustments. Firebird 1.0 Quick Start Guide 7 Testing your installation If everything works as designed, the Firebird server process will be running on data- base - unable to open database”, the server probably isn't running. In that case, go back to Testing your installation and fix the problem. Let's say you decide to change the SYSDBA password to icuryy4me

will do .................................................................................... 36 Testing your Linux installation ........................................................................ likely to be whether to use Classic or Superserver. For development, there's nothing in it. For testing and deployment, the choice may be more important. Superserver's shared page cache, properly configured entry to aliases.conf for the sample database, employee.fdb. Installing on POSIX Platforms 37 Testing your Linux installation Step 1 - Accessing a database In a shell: $cd /opt/firebird/bin $./isql

Transactions There are a couple of problems with limbo transactions as discovered by Paul in his testing. 18.4.1. Limbo Transaction Options — All The Same? When processing limbo transactions, it appears the option to commit, rollback or neither. 18.4.2. Limbo Transactions — Can Be Backed Up Paul’s testing of limbo transactions revealed that it is possible to make a backup of a database with limbo transactions

a separate utility as it can split files using the split command as well as using gbak.  In testing with Firebird 1.5 and Firebird 2.0 on Windows XP Home and WIndows 2000, gsplit doesn’t seem to work

so on, of the original database but none of the data. This can be useful when you have finished testing your application in a test environment and wish to migrate the system to a production environment

be ignored. The details displayed will always be for the current database. SQL> show database testing_db; Database: employee Owner: SYSDBA PAGE_SIZE 4096 ... Default Character set: NONE You

data are not recommended for use as keys or to have uniqueness constraints applied to them. For testing data in columns with floating-point data types, expressions should check using a range, for instance constraint. 2. When a new CHECK constraint is added, existing data is not tested for compliance. Prior testing of existing data against the new CHECK expression is recommended. 3. Although adding an identity a bug, which will be fixed in Firebird 5.0 (and — maybe — Firebird 4.0.3), see issue #7256.  Testing a blob for NULL using the IS [NOT] NULL operator does not read it and therefore a temporary blob