Re: ECPG problem with 8.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: ECPG problem with 8.3
Date: 2008-01-14 15:57:45
Message-ID: 14708.1200326265@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk> 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 a simple workaround. Just sprintf the
>> statement to a string and thereby replace the count variable with its
>> content and then EXEC SQL EXECUTE the string variable should do the job.

> Fetch with a variable seems to be almost the only useful way of using FETCH
> ABSOLUTE (or any of the variants that have count parameter).

> For backwards compatibility wouldn't it be better to do the sprintf in
> the ECPG preprocessor if the count is a variable rather than generate
> an error?

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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-01-14 15:58:56 Re: Forgot to dump old data before re-installing machine
Previous Message Tom Lane 2008-01-14 15:46:07 Re: tcp_keepalives_idle ignored