From: Olivier M. <om...@in...> - 2015-11-12 22:19:07
|
Hi Marius, > Le 11 nov. 2015 à 13:33, marius adrian popa <ma...@gm...> a écrit : > > For firebird 3.0 i would contribute back in the main firebird repository and use and document the new api Maybe it could make sense for a Flamerobin version dedicated to Firebird 3 to use its newer 'interfaces' API, unwrapped. But believe me - or not :) - for large C++ business applications, the naked Firebird 3 'interfaces' API is simply a no-go. I like the idea that it's very thin and low-level oriented, despite it using some C++ classes: for this I'd call it a 'C' 2.0 API and I see it very well suited for being used by middleware developers. But you can't ask a business application developer to talk to the database using that API. There are simply too much technical details to take into account. It's obviously better than with the antique isc_ C API. But still way too much details to keep the focus of any business C++ programming on the real task at hand instead of the details of interfacing with the database. I hope people will correctly see my point: I'm not disparaging that new API. I'm just saying it is not designed for use by programmers who's job is about their own code rather than how to deal with the database to get the job done. :) It needs some wrapper to make it easier to use for a whole class of developers. There certainly is room for an even higher abstraction level than IBPP brought to the isc_ antique API. -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om |