aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/trigger.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2001-08-02 15:45:55 +0000
committerBruce Momjian <bruce@momjian.us>2001-08-02 15:45:55 +0000
commit84d2c518fe24e5b95b8113ff175ac5c13d2869d2 (patch)
treecb17caac17d0d944926fdb1eaefab98da5d4568c /src/backend/commands/trigger.c
parentd00b272299f1fdccfcca9c8df183f1cfc35cbb54 (diff)
downloadpostgresql-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 'src/backend/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions