| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parameterized fetch |
| Date: | 2005-09-14 22:54:06 |
| Message-ID: | 4328AA0E.7090202@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure wrote:
> I've noticed that trying to parameterize a fetch statement via
> ExecParams returns a syntax error:
>
> fetch $1 from my_cursor;
>
> This is not really a big deal, but maybe it should be documented which
> statements can be parameterized and which can't
Currently the documentation is "the backend's grammar". You can only put
parameters where there is a PARAM node, which currently means "anywhere
you can put a c_expr". So if you can replace something with an
expression, you can probably also replace it with a parameter.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2005-09-15 01:03:16 | Re: inverse OR distributive law? |
| Previous Message | Kris Jurka | 2005-09-14 22:04:55 | Re: GSSAPI or Kerberos authentication problems |