* markw@mohawksoft.com (markw@mohawksoft.com) wrote:
> > * markw@mohawksoft.com (markw@mohawksoft.com) wrote:
> >> Looking at both ODBC and libpq and I think that the difference is that
> >> libpq aims to make PostgreSQL interfacing easy, while ODBC strives to be
> >> a
> >> comprehensive SQL interface. 99% of what will be done with the ODBC
> >> interface will be simple SQLAllocStmt, SQLPrepare, and SQLExecute.
> >
> > Saying what 99% of what the ODBC driver does isn't terribly useful-
> > What's that 1% that libpq can't do? Having looked at the code, can you
> > give us an idea on that?
>
> Off the top of my head, binding data to the SQL statement, reusing
> statements, stuff like that.
Isn't this handled by PQexecParams and PQexecPrepared?
> The ODBC API isn't designed to talk to any one database, so there are no
> short cuts. Unfortunately, applications based on ODBC assume there are no
> short cuts, and rely on that behavior.
That's not particularly relevant- the question is if the existing libpq
API is sufficient for the ODBC driver or not.
Stephen