Coexistence of Firebird 1.5 and InterBase 5.6 or 6.0 Brenden Walker Paul Vinkenoog 8 April 2005 - Document version 1.2.1 2 Table of Contents Introduction ......................................... ...................................................................... 3 Running Firebird and InterBase together ...................................................................................... .......................................................................... 3 Switching between InterBase and Firebird ..................................................................................

still uses many of the same locations, component names and resource links as InterBase 6.x and prior versions of InterBase. Hence, it is not possible to run both a Firebird server and an In- terBase server possibly other UNIX distros Installation directory (referred to hereafter as ) /opt/interbase Firebird server ibserver (SS) or gds_inet_server (CS) /bin Command-line tools gbak Windows Control Panel applets Pre-1.0 distributions of Firebird for Windows kits installed the InterBase Manager applet into the Control Panel of operating systems that support services. It was omitted

database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.5.1. Older InterBase and Firebird versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . be used only for legacy databases that were first created Chapter 2. Generator Basics 4 under InterBase 5.6 or earlier. One of the differences between the two is that dialect 1 has no native 64-bit integer like. Chapter 2. Generator Basics 5 2.5.1. Older InterBase and Firebird versions In the earliest pre-1.0 Firebird versions, as well as in InterBase, only one database page was used to store the generator

SET A = x, B = y, A = z will be 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 of performance loss: Existence Predicates NOT IN and ALL May Be Slow Firebird and, before that, InterBase, have produced incorrect results for the logical existence predicates ALL and NOT IN for many years at the start of the previous chapter. • If you already have an earlier version of Firebird or InterBase® on your server and you think you might want to go back to it, set up your fall-back position before

licenses: the IPL (InterBase Public License) and the IDPL (Initial Developer's Public License). The first one covers the parts of the source code that were inherited from InterBase; the second applies are upgrading from a previous version or if there are remnants of an old (and maybe long gone) InterBase or Firebird installation floating around your system (DLLs, Registry entries, environment variables operation of multiple servers on a single machine. It can also run concurrently with Firebird 1.x or InterBase servers. Setting this up is not a beginner's task though. If you need to run multiple servers, consult

licenses: the IPL (InterBase Public License) and the IDPL (Initial Developer’s Public License). The first one covers the parts of the source code that were inherited from InterBase; the second applies are upgrading from a previous version or if there are remnants of an old (and maybe long gone) InterBase or Firebird installation floating around your system (DLLs, Registry entries, environment variables…) operation of multiple servers on a single machine. It can also run concurrently with Firebird 1.x or InterBase servers. Setting this up is not a beginner’s task though. If you need to run multiple servers on

2 Types TStatusVector = Array[0..19] of ISC_STATUS TStatusVector is the (opaque) type of the Interbase internal status vector. 613 CHAPTER 20. REFERENCE FOR UNIT ’IBCONNECTION’ 20.3 TDatabaseInfo information about the connected database. 20.4 EIBDatabaseError 20.4.1 Description Firebird/Interbase database error, a descendant of db.EDatabaseError (613). See also: db.EDatabaseError (613) 20 20.4.2 Property overview Page Properties Access Description 614 GDSErrorCode r Firebird/Interbase GDS error code. 614 StatusVector rw Low-level IB API status vector 20.4.3 EIBDatabaseError.StatusVector

the client and received from the server. The described protocol is Firebird/Interbase protocol version 10. Earlier (Interbase) versions of the protocol are not in scope for this document. Changes in later version 11 is partially described). This document is not complete. It is advisable to consult the Interbase 6.0 API Guide for additional information on subjects like parsing the status vector, information operation). Byte[] Status vector  Information about parsing the status vector can be found in the Interbase 6.0 API Guide in the documentation set. It might also be advantageous to look at the sources of

be used. It has been deprecated. Its purpose is to force the backup to be made using the older InterBase versions' format of meta data descriptions. -PAS[SWORD] See above. -RO[LE] Chapter 4. Restore Mode Backups taken with the gbak application from one version of Firebird — or InterBase — can be used by later versions of Firebird to restore the database, however, while this may result Structure (ODS) for the database in question, the SQL Dialect will never be changed. If you backup an InterBase dialect 1 database and then use the dump file to recreate it under Firebird 2.1, for example, the

condition. Before returning true it must step through the entire set. 5.3.2. SINGULAR SINGULAR is an InterBase/Firebird extension to the SQL standard. It is often described as returning true if exactly one but defined in separate modules. Firebird ships with two UDF libraries: ib_udf (a widely used “InterBase library”) and fbudf. You can add more libraries, e.g. by buying or downloading them, or by writing empty string). The main cause of this problem is that with “old style” UDF calling (inherited from InterBase), it is not possible to pass NULL as input to the function. When a UDF like LTRIM (left trim) is