From: | Shelby Cain <alyandon(at)yahoo(dot)com> |
---|---|
To: | Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk>, 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:36:50 |
Message-ID: | 589617.74312.qm@web55402.mail.re4.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- Original Message ----
> From: Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk>
> To: Michael Meskes <meskes(at)postgresql(dot)org>; pgsql-general(at)postgresql(dot)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
>
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'd like to add to this discussion from an Oracle Pro*C (Oracle's name for embedded SQL) perspective. Most of the Pro*C code that I've worked with over the years uses a variable for the fetch count as well. It'd be nice if there was some way to support this convention directly in ECPG (assuming it doesn't create maintenance/security issues) for anyone porting applications from Oracle to Postgresql.
Regards,
Shelby Cain
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-14 15:39:17 | Re: ERROR: shared buffer hash table corrupted |
Previous Message | Tom Lane | 2008-01-14 15:36:08 | Re: Index trouble with 8.3b4 |