Subject | Re: [Firebird-general] RE: MySQL versus Firebird |
---|---|
Author | Peter Faulks |
Post date | 2014-03-11T03:58:30Z |
On 11/03/2014 2:02 PM, Paul Vinkenoog wrote:
postgres, sqlite and even mySqL have usable (useful if you like) C (NB
'C' not C++) api's. Firebird's is a pile of puss.
Where might I find the release notes? - Are they in the bottom of a
locked filing cabinet stuck in a disused lavatory with a sign on the
door saying 'Beware of the Leopard' ???
> <faulksp@...> wrote:You have a strange understanding of the word 'usable'.
>
> > A usable C API would be a good one to add to the list
> >
> > This is the reason I don't use Firebird anymore. I keep coming back
> for another look every now and again, but it seems actually being able
> to use the database engine in a meaningful way doesn't seem to have any
> priority.
>
> Countless people - developers as well as end users - use this database
> engine "in a meaningful way" on a daily basis.
>
> What exactly is your problem? Yes, the C API is ugly (like many C APIs).
> But it's usable, and you can write your own wrapper around it or use one
> of the existing connectivity toolsets.
>
> Anyway, next time you come back here for another look, maybe you should
> check out the Firebird 3 Alpha 2 Release Notes, section "Application
> Programming Interfaces".
postgres, sqlite and even mySqL have usable (useful if you like) C (NB
'C' not C++) api's. Firebird's is a pile of puss.
Where might I find the release notes? - Are they in the bottom of a
locked filing cabinet stuck in a disused lavatory with a sign on the
door saying 'Beware of the Leopard' ???