| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Todd A(dot) Cook" <tcook(at)blackducksoftware(dot)com> |
| Cc: | pgsql-general(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Is "query" a reserved word in 8.3 plpgsql? |
| Date: | 2007-11-09 23:14:16 |
| Message-ID: | 4149.1194650056@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Todd A. Cook" <tcook(at)blackducksoftware(dot)com> writes:
> I saw the item in the release notes about the new "return query"
> syntax in pl/pgsql, but I didn't see any note about "query" being
> reserved now. Perhaps an explicit mention should be added?
Yeah, I got burnt by that too. I have a bad feeling that that keyword
is going to cause trouble for a lot of people.
[ thinks for a bit... ] It might be possible to get rid of the keyword
and have RETURN QUERY be recognized by an ad-hoc strcmp test, much like
the various direction keywords in FETCH have been handled without making
them real keywords. It'd be a bit uglier but it'd avoid making QUERY
be effectively a reserved word.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | paul rivers | 2007-11-09 23:25:58 | Enabling password complexity for password authentication |
| Previous Message | Bruce Momjian | 2007-11-09 23:07:03 | Re: any way to query for current connections to db? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2007-11-09 23:39:31 | Re: Segmentation fault using digest from pg_crypto |
| Previous Message | Tom Lane | 2007-11-09 22:16:32 | Re: last note to rewrite function |