I'd go with ecpg as there are similar facilities in other,
commercial, databases. So, if you ever need to write
portable applications that'd be a way to achieve it.
libpq is very PostgreSQL-specific.

Look out for our new book (due August/September)
called "Beginning Databases with PostgreSQL"
which covers database principles and PostgreSQL
including libpq and ecpg.

Regards
Neil Matthew

----- Original Message -----
From: <millward@m...>
To: Pro Linux Programming <pro_linux_programming@p...>
Sent: 05 August 2001 20:49
Subject: [pro_linux_programming] PostgreSQL, libpg or ecpg?


> Is there an 'industry standard' for programming
> to PostgreSQL database?  libpg or ecpg?
> I want to get used to the way I might have to
> program in a job setting. I know SQL so I'm
> leaning towards ecpg.  Any opinions out there?
> ---