Move to OOP API?

[MartinKoeditz]

Maybe it's time to merge the code from satware

They did a rewrite based on the modern OOP API.
The extension is called "firebird.so". The functions are called fbird_*.

What do you think?

[mlazdans]

I've seen the progress but I haven't yet checked it. Have you used it?

[MartinKoeditz]

I will check it next days. I already did some code examinations. Looks much cleaner than the old interbase code. So it will be more maintainable.

If it's ok we'll have to decide if we do a hard cut or a smooth one keeping the ibase_* functions.

[mlazdans]

Satware looks very nice on the surface but I have not taken a deeper look yet. This could can take over as new extension but
existing code should be kept as legacy somewhere I think. Maybe even forked into it's own, separate repo. Because legacy codebases won't benefit much from absolutely new, mostly incompatible version.

[emil-totev]

I have been looking at that, currently using their version 8.0.0 and looks OK. Didn't use newer versions, it all happens too fast..
From compatibility pov, they also renamed the IBASE_ constants, not only the functions.
And please keep in mind there is AI involved there, so everything should better be double-checked.

From my point of view, it would be best if the old interbase extenison exports only ibase_* functions and constants, and the new firebird extension exports only fbird_* functions and constants, and then they could even be loaded side-by-side for tests and comparisons.