From: | Samuel PHAN <samuel(at)nomao(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Add SPI results constants available for PL/* |
Date: | 2012-01-03 10:55:41 |
Message-ID: | CAC4O=ams2wGNDVujA6_2OAGOQ=ay-ZMyfcEB0gbAnHutKdWyWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I'm using PL/Python, and when getting the result object from a
plpy.execute(), I can access to the result.status().
E.g.: the result.status() is 4. But to know what 4 corresponds to, I must
open the "spi.h" file from the sources to see :
#define SPI_OK_CONNECT 1
#define SPI_OK_FINISH 2
#define SPI_OK_FETCH 3
#define SPI_OK_UTILITY 4
#define SPI_OK_SELECT 5
#define SPI_OK_SELINTO 6
#define SPI_OK_INSERT 7
#define SPI_OK_DELETE 8
#define SPI_OK_UPDATE 9
#define SPI_OK_CURSOR 10
#define SPI_OK_INSERT_RETURNING 11
#define SPI_OK_DELETE_RETURNING 12
#define SPI_OK_UPDATE_RETURNING 13
#define SPI_OK_REWRITTEN 14
Is there a way to have access to these constants from the PL/python code
and other PL/* (Tcl, Perl, etc.) ?
Thanks,
--
Samuel PHAN
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-01-03 11:08:37 | Re: review: CHECK FUNCTION statement |
Previous Message | Simon Riggs | 2012-01-03 10:47:17 | Re: ALTER TABLE lock strength reduction patch is unsafe |