Thread: native api or odbc?

I use odbc in a windows environment.

No complaints, can do inserts, select, updates, joins, execute stored procedures
with little fuss...more than fast enough for my purposes.

There are some issues with 32/64 bit odbc depending on your relative
OS..as far as installing the correct odbc version. To be expected

Otherwise I couldn't be happier. For what it's worth.


On Tue, 2015-06-23 at 15:56 -0700, Ted Toth wrote:

What are peoples experiences with either/both, pluses/minuses?

Ted

On 6/23/2015 3:56 PM, Ted Toth wrote:
> What are peoples experiences with either/both, pluses/minuses?
>

ODBC adds a whole layer of obfuscation which, IMHO, if you know you're
only dealing with PostgreSQL, is infuriating.

I'd rather program the native API, its just much cleaner and simpler,
unless you're using a programming framework that has native ODBC support
built in.



--
john r pierce, recycling bits in santa cruz

----- Original Message -----
From: Bret Stern

>I use odbc in a windows environment.

>No complaints, can do inserts, select, updates, joins, execute stored
>procedures
with little fuss...more than fast enough for my purposes.

>There are some issues with 32/64 bit odbc depending on your relative
OS..as far as installing the correct odbc version. To be expected

>Otherwise I couldn't be happier. For what it's worth.

+1

>>On Tue, 2015-06-23 at 15:56 -0700, Ted Toth wrote:
>>What are peoples experiences with either/both, pluses/minuses?



>>Ted

On Tue, Jun 23, 2015 at 5:56 PM, Ted Toth <txtoth@gmail.com> wrote:
> What are peoples experiences with either/both, pluses/minuses?

If you're coding at the C level, I would definitely choose libpq
unless you were worried about cross database portability.   libpq is a
bit clunky but easy to code against.  libpq is also easier to
configure and port than odbc.

merlin