database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

Remove the prohibition on executing cursor commands through SPI_execute.

Browse Source 
Vadim had included this restriction in the original design of the SPI code,
but I'm darned if I can see a reason for it.

I left the macro definition of SPI_ERROR_CURSOR in place, so as not to
needlessly break any SPI callers that are checking for it, but that code
will never actually be returned anymore.
This commit is contained in:
Tom Lane
2007-03-25 23:27:59 +00:00
parent e85a01df67
commit bf8236526b
4 changed files with 6 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/spi.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.54 2007/03/15 23:12:06 tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.55 2007/03/25 23:27:59 tgl Exp $ -->
<chapter id="spi">
<title>Server Programming Interface</title>
@ -554,21 +554,11 @@ typedef struct
</listitem>
</varlistentry>
<varlistentry>
<term><symbol>SPI_ERROR_CURSOR</symbol></term>
<listitem>
<para>
if <command>DECLARE</>, <command>CLOSE</>, or <command>FETCH</>
was attempted
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><symbol>SPI_ERROR_TRANSACTION</symbol></term>
<listitem>
<para>
if any command involving transaction manipulation was attempted
if a transaction manipulation command was attempted
(<command>BEGIN</>,
<command>COMMIT</>,
<command>ROLLBACK</>,