| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Preventing some SQL commands |
| Date: | 2004-11-21 18:35:17 |
| Message-ID: | 9137.1101062117@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Hallgren <thhal(at)mailblocks(dot)com> writes:
> In a PL language it's sometimes desirable to prevent execution of some
> commands. I would like to prevent the commands "begin [work or
> transaction]", "commit", and "rollback", completely and I would like to
> force the user to use explicit methods for the savepoint methods.
If you are executing through SPI then those operations are disallowed
already.
> I wonder if there's any way to extract the nature of a command from the
> execution plan returned by SPI_prepare. If not, would it be very
> difficult to add?
The main problem with this proposal is the erroneous assumption that
there can be only one command in a SPI plan.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James William Pye | 2004-11-21 20:06:03 | Re: Preventing some SQL commands |
| Previous Message | Robert Treat | 2004-11-21 18:26:36 | Re: bug/issue tracking system? |