| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: PQprepare case sensitive? |
| Date: | 2007-06-08 14:58:30 |
| Message-ID: | 20070608145830.GB18853@feivel.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Fri, Jun 08, 2007 at 09:56:42AM -0400, Tom Lane wrote:
> Yes, it's assumed that any quoting/dequoting has already happened by the
> time the name gets into the protocol message.
But shouldn't this be documented? I failed to find it. But then this
wouldn't be the first time I fail to find the right place in
documentation.
> > I wonder because a statement like this cannot be
> > deallocated afterwards since the parser is case insensitive with regard
> > to statement names.
>
> Sure it can --- use quotes.
True of course. My wording was bad. I meant with the same way of writing
the name.
Again, I have no problem with this behaviour I just wanted to make sure
it's supposed to be this way before I start implementing ecpg's handling
of this.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-08 15:05:28 | Re: PQprepare case sensitive? |
| Previous Message | Tom Lane | 2007-06-08 13:56:42 | Re: PQprepare case sensitive? |