[fpc-pascal] Re: Interbase vs Firebird header translation

[LacaK]

> Regarding FB2/FB3, FYI please note this snippet in the other thread: my
> post and Michael's reply:
>   
>>> OT: that would be useful for another reason.
>>> Firebird 3 will introduce the BOOLEAN datatype and other innovations
>>> (encrypted connections, etc).
>>> Interbase has had BOOLEAN support for a while now.
>>>
>>> It would be nice to be able to support new functionality without
>>> sacrificing the ability to connect to older clients.
>>>       
To be concrete: take as example BOOLEAN datat type:

Firebird 3.0:
-------------
#define SQL_BOOLEAN                32764 // new in Firebird 3.0
#define SQL_NULL                         32766 // new in Firebird 2.5


Interbase 7.0 (For ESQL and DSQL programmers, we define the following 
type in ibase.h:):
--------------
#define SQL_BOOLEAN 590 ... ;-))

So how we should update ibase60.inc ?
Add both ? (SQL_BOOLEAN_INTERBASE=590, SQL_BOOLEAN_FIREBIRD=32764 ... 
and support both in one TIBConnection ... I expect, that data will be in 
both cases as 0/1 signed short ) ... it seems to me easier!

Or split header files ... but then we must also create TFBConnection 
(like TIBConnection) ? ... it seems to me more complicated ATM

-Laco.