Michael Meskes wrote:
On Fri, Feb 29, 2008 at 11:27:25AM -0500, Steve Clark wrote:
Actually it appears to work in 8.2.5 but be broken in 8.2.6 and 8.3.0.
Are you really sure? It appears to me that there was no change between
8.2.5 and 8.2.6 that could affect ecpg's handling of arrays of
Michael Meskes wrote:
I just committed the attached small fix to CVS HEAD and the 8.3 branch.
This should fix your problem.
Michael
diff --exclude CVS -ru /home/postgres/pgsql-ecpg/preproc/type.c preproc/type.c
---
I just committed the attached small fix to CVS HEAD and the 8.3 branch.
This should fix your problem.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF
On Fri, Feb 29, 2008 at 11:27:25AM -0500, Steve Clark wrote:
Actually it appears to work in 8.2.5 but be broken in 8.2.6 and 8.3.0.
Are you really sure? It appears to me that there was no change between
8.2.5 and 8.2.6 that could affect ecpg's handling of arrays of varchar.
Michael
--
Michael
Steve Clark wrote:
Hello List,
Don't know whether anyone here can help but... We have some code that
has compiled and ran just
fine from postgresql 7.3.x thru 8.2.6. It uses embedded sql. I just
yesterday upgraded our test system to
8.3.0 and this code will no longer compile. Below is a
Hello List,
Don't know whether anyone here can help but... We have some code that
has compiled and ran just
fine from postgresql 7.3.x thru 8.2.6. It uses embedded sql. I just
yesterday upgraded our test system to
8.3.0 and this code will no longer compile. Below is a standalone code
fragment
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
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.
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
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,
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
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
- 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 be almost the only useful way of
using
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 there is
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: error:
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'
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
17 matches
Mail list logo
