diff options
| author | Bruce Momjian <bruce@momjian.us> | 2001-08-02 15:45:55 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2001-08-02 15:45:55 +0000 |
| commit | 84d2c518fe24e5b95b8113ff175ac5c13d2869d2 (patch) | |
| tree | cb17caac17d0d944926fdb1eaefab98da5d4568c /doc/src | |
| parent | d00b272299f1fdccfcca9c8df183f1cfc35cbb54 (diff) | |
| download | postgresql-84d2c518fe24e5b95b8113ff175ac5c13d2869d2.tar.gz postgresql-84d2c518fe24e5b95b8113ff175ac5c13d2869d2.zip | |
I noticed that pltcl didn't have any way to get to SPI_lastoid like plpgsql does.. I started using pltcl a lot because I like to decide when and how my queries get planned.. so I put one together really quick
Sorry I don't have the original around to make a quick diff, but its a very small change... I think this should be in the next release, there's no reason not to have it.
its a function with no expected arguments, so you can use it like:
spi_exec "INSERT INTO mytable(columns...) VALUES(values..)"
set oid [spi_lastoid]
spi_exec "SELECT mytable_id from mytable WHERE oid=$oid"
It just didn't make sense for me to use plpgsql and pltcl, or just screw
them both and use SPI from C.
bob@redivi.com
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/pltcl.sgml | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/src/sgml/pltcl.sgml b/doc/src/sgml/pltcl.sgml index 0683739f1a4..75698467607 100644 --- a/doc/src/sgml/pltcl.sgml +++ b/doc/src/sgml/pltcl.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/pltcl.sgml,v 2.11 2001/06/09 02:19:07 tgl Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/pltcl.sgml,v 2.12 2001/08/02 15:45:55 momjian Exp $ --> <chapter id="pltcl"> @@ -395,6 +395,18 @@ CREATE TRIGGER trig_mytab_modcount BEFORE INSERT OR UPDATE ON mytab </varlistentry> <varlistentry> + <indexterm> + <primary>spi_lastoid</primary> + </indexterm> + <term>spi_lastoid</term> + <listitem> + <para> + Returns the OID of the last query if it was an INSERT. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term>spi_exec ?-count <replaceable>n</replaceable>? ?-array <replaceable>name</replaceable>? <replaceable>query</replaceable> ?<replaceable>loop-body</replaceable>?</term> <listitem> <para> |