Re: [GENERAL] ECPG problem with 8.3

2008-01-30 Thread Peter Wilson
Michael Meskes wrote: On Mon, Jan 14, 2008 at 10:57:45AM -0500, Tom Lane wrote: I'm concerned about this too. We'll at least have to call this out as an incompatibility in 8.3, and it seems like a rather unnecessary step backwards. Given that people seem to use this feature I'm more t

Re: [GENERAL] ECPG problem with 8.3

2008-01-15 Thread Peter Wilson
them. Every one can say this; every one can call himself a prophet. But I see that Christian religion wherein prophecies are fulfilled; and that is what every one cannot do. 694. And what crowns all this is prediction, so that it should not be said that it is chance which has done it? Whosoever,

Re: [GENERAL] ECPG problem with 8.3

2008-01-15 Thread Peter Wilson
That it had been her opinion, till now, she was not guilty of Adam's sin, nor any way concerned in it, because she was not active in it; but that now she saw she was guilty of that sin, and all over defiled by it; and the sin which she brought into the world with her, was alone sufficient to condem

Re: [GENERAL] ECPG problem with 8.3

2008-01-15 Thread Michael Meskes
On Mon, Jan 14, 2008 at 10:57:45AM -0500, Tom Lane wrote: > I'm concerned about this too. We'll at least have to call this out as > an incompatibility in 8.3, and it seems like a rather unnecessary step > backwards. I thought I had send an email asking for comments back when this was implemented.

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Tom Lane
Peter Wilson <[EMAIL PROTECTED]> writes: > Michael Meskes wrote: >> Yes. ECPG move to the latest backend protocol version to be able to >> prepare statements correctly. However, with this protocol my own >> addition to the standard, namely a variable as fetch count, is not >> supported anymore. But

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Shelby Cain
- Original Message > From: Peter Wilson <[EMAIL PROTECTED]> > To: Michael Meskes <[EMAIL PROTECTED]>; pgsql-general@postgresql.org > Sent: Monday, January 14, 2008 8:41:12 AM > Subject: Re: [GENERAL] ECPG problem with 8.3 > > Fetch with a variable seems to

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Peter Wilson
Michael Meskes wrote: On Sun, Jan 13, 2008 at 03:01:04PM +, Peter Wilson wrote: that fixes that problem. My build now gets further, but I get an error and a seg-fault later in the build. Whow, you're really stress testing it. Thanks a lot! This is what we need. I have to say I didn't wri

Re: [GENERAL] ECPG problem with 8.3

2008-01-14 Thread Michael Meskes
On Sun, Jan 13, 2008 at 03:01:04PM +, Peter Wilson wrote: > that fixes that problem. My build now gets further, but I get an error > and a seg-fault later in the build. Whow, you're really stress testing it. Thanks a lot! This is what we need. > Apart from the seg-fault, is there any particu

Re: [GENERAL] ECPG problem with 8.3

2008-01-13 Thread Peter Wilson
Michael Meskes wrote: On Fri, Jan 11, 2008 at 11:51:08PM +, Peter Wilson wrote: I've just tried compiling our project against the 8.3RC1 code. This is the first time I've tried any release of 8.3. ... crbembsql.pgC:254: error: invalid conversion from `int' to `ECPG_statement_type' crbembsql

Re: [GENERAL] ECPG problem with 8.3

2008-01-13 Thread Michael Meskes
On Fri, Jan 11, 2008 at 11:51:08PM +, Peter Wilson wrote: > I've just tried compiling our project against the 8.3RC1 code. This is > the first time I've tried any release of 8.3. > ... > crbembsql.pgC:254: error: invalid conversion from `int' to > `ECPG_statement_type' > crbembsql.pgC:254: er

[GENERAL] ECPG problem with 8.3

2008-01-11 Thread Peter Wilson
I've just tried compiling our project against the 8.3RC1 code. This is the first time I've tried any release of 8.3. Several components use ECPG. I'm now getting an ECPG error. Compiling on 8.2.3 is fine. I've checked the 8.3 release documentation and there don't seem to be any that change the