| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Boszormenyi Zoltan <zb(at)cybertec(dot)at> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Meskes <meskes(at)postgresql(dot)org>, Hans-Juergen Schoenig <hs(at)cybertec(dot)at> |
| Subject: | Re: ECPG fix for mixed case cursor names |
| Date: | 2010-09-02 02:59:33 |
| Message-ID: | AANLkTinYhC11BrG+Qiyi=of6yomHJcuv73GBy-zAJ0gy@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/8/25 Boszormenyi Zoltan <zb(at)cybertec(dot)at>:
> PostgreSQL allows in plain SQL to declare a cursor
> e.g. in all lower case and fetch from is in all upper case.
> We need to allow this from ECPG, too, but strictly when
> the cursor name is not in a variable. Otherwise this code
> below doesn't notice the cursor's double declaration
> and complains using an undeclared cursor:
It might be a good idea to add this to the open CommitFest so we don't
lose track of it.
https://commitfest.postgresql.org/action/commitfest_view/open
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-09-02 03:00:39 | Re: Rewrite, normal execution vs. EXPLAIN ANALYZE |
| Previous Message | Robert Haas | 2010-09-02 02:58:13 | Re: multibyte charater set in levenshtein function |