On Mon, Apr 02, 2007 at 09:06:17PM -0400, Bruce Momjian wrote:
>
> Michael, is there any progress on this?
> ---
> > So this essantially is only to get an error message into the connection
> > structure. However, having an emp
Michael, is there any progress on this?
---
Michael Meskes wrote:
> On Mon, Mar 19, 2007 at 09:48:19AM +0100, Magnus Hagander wrote:
> > > Q2. Do we need to use PQescapeStringConn() instead of PQescapeString()?
> > >PQes
On Mon, Mar 19, 2007 at 09:48:19AM +0100, Magnus Hagander wrote:
> > Q2. Do we need to use PQescapeStringConn() instead of PQescapeString()?
> >PQescapeString() is used to escape literals, and the documentation says
> >PQescapeStringConn() should be used in multi-threaded client programs.
>
On Mon, Mar 19, 2007 at 09:33:54AM +0900, ITAGAKI Takahiro wrote:
>
> Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> > This patch replaces the pthreads code in ecpg with native win32 threads,
> > in order to make it threadsafe. The idea is not to have to download the
> > non-standard pthreads lib
Magnus Hagander <[EMAIL PROTECTED]> wrote:
> This patch replaces the pthreads code in ecpg with native win32 threads,
> in order to make it threadsafe. The idea is not to have to download the
> non-standard pthreads library on windows.
>
> Does it seem like it should be doing the right thing? Do
This patch replaces the pthreads code in ecpg with native win32 threads,
in order to make it threadsafe. The idea is not to have to download the
non-standard pthreads library on windows.
Does it seem like it should be doing the right thing? Does somebody have
a good test-case where ecpg breaks whe
