IBX for Lazarus 2.7.11 and 2.7.12 released

[rvk]

I can probably do this without impacting current users - although I am mystified as to why anyone would still want to use Firebird 1.5. If you want to upgrade an existing FB1.5 database then gbak can always be used to upgrade the DB to a more recent version.

If that's the philosophy then you could also strip out all the older 1.5 and ODS10 stuff   

What is the oldest Firebird IBX for Lazarus officially supports?
There could still be someone with a userbase which are on 1.5 (not ready to upgrade).

(for me most are on 2.5 and a couple on 2.1)

[tonyw]

I can probably do this without impacting current users - although I am mystified as to why anyone would still want to use Firebird 1.5. If you want to upgrade an existing FB1.5 database then gbak can always be used to upgrade the DB to a more recent version.

If that's the philosophy then you could also strip out all the older 1.5 and ODS10 stuff   

What is the oldest Firebird IBX for Lazarus officially supports?
There could still be someone with a userbase which are on 1.5 (not ready to upgrade).

(for me most are on 2.5 and a couple on 2.1)

Point taken. I never have stated an oldest Firebird release supported. The approach has been to leave old conditional code in place and only fix it if a problem is reported. So I guess this fix comes under that heading.

[maurog]

Hi Tony,

Thank you very much for your reply — and for the clarification
regarding IBX's version support policy.

My underlying idea behind this patch was not to create new Firebird
1.5 databases, but to give users a way to rescue their old data.
With this small patch I can now open Firebird 1.5 databases in
TurboBird and at least export the data (CSV, JSON, etc.).

I could ship the minimal required Firebird 1.5 files (client library,
etc.) along with TurboBird, so that the user can rescue their old
data in embedded (local) mode without needing a FB 1.5 installation
of their own — provided that is technically feasible at all.

Currently I am running Firebird 1.5 in server mode; for shipping
with TurboBird, however, the embedded mode would be the more elegant
solution, since the user would then not need their own FB 1.5
installation.

To be honest, I also have my own concerns regarding this patch:
that I might stumble over it elsewhere in TurboBird, because IBX
does not fully support Firebird 1.5.

Thank you once again for even taking a look at it.

Best regards,
Maurog.

[maurog]

Hi Tony,

while testing IBX with Firebird 6, I encountered a reproducible
behavior with NUMERIC columns of precision > 16. Note that
Firebird itself supports NUMERIC precision up to 38.

Reproduction:
  - Source: FB 6, table with NUMERIC(38,10)
  - Target: FB 6
  - Copy via TIBQuery with parameter binding
  - Value: 12345.6789 (only 9 significant digits)

Error message:
  "BCD Precision (17) is too large for Firebird Data Type
   max precision (16)"

The value actually has only 9 significant digits, but IBX
detects a precision of 17. Is this a known behavior or a bug
in the precision handling?

Best regards,
Maurog.