postgresql/src/pl/plpython/plpy_resultobject.h

/*
 * src/pl/plpython/plpy_resultobject.h
 */

#ifndef PLPY_RESULTOBJECT_H
#define PLPY_RESULTOBJECT_H

#include "access/tupdesc.h"


typedef struct PLyResultObject
{
	PyObject_HEAD
	/* HeapTuple *tuples; */
	PyObject   *nrows;			/* number of rows returned by query */
	PyObject   *rows;			/* data rows, or empty list if no data
								 * returned */
	PyObject   *status;			/* query status, SPI_OK_*, or SPI_ERR_* */
	TupleDesc	tupdesc;
} PLyResultObject;

extern void PLy_result_init_type(void);
extern PyObject *PLy_result_new(void);

#endif   /* PLPY_RESULTOBJECT_H */
Split plpython.c into smaller pieces This moves the code around from one huge file into hopefully logical and more manageable modules. For the most part, the code itself was not touched, except: PLy_function_handler and PLy_trigger_handler were renamed to PLy_exec_function and PLy_exec_trigger, because they were not actually handlers in the PL handler sense, and it makes the naming more similar to the way PL/pgSQL is organized. The initialization of the procedure caches was separated into a new function init_procedure_caches to keep the hash tables private to plpy_procedures.c. Jan Urbański and Peter Eisentraut 2011-12-18 14:14:16 -05:00			`/*`
			`* src/pl/plpython/plpy_resultobject.h`
			`*/`

			`#ifndef PLPY_RESULTOBJECT_H`
			`#define PLPY_RESULTOBJECT_H`

PL/Python: Add result metadata functions Add result object functions .colnames, .coltypes, .coltypmods to obtain information about the result column names and types, which was previously not possible in the PL/Python SPI interface. reviewed by Abhijit Menon-Sen 2012-01-30 14:38:52 -05:00			`#include "access/tupdesc.h"`


Split plpython.c into smaller pieces This moves the code around from one huge file into hopefully logical and more manageable modules. For the most part, the code itself was not touched, except: PLy_function_handler and PLy_trigger_handler were renamed to PLy_exec_function and PLy_exec_trigger, because they were not actually handlers in the PL handler sense, and it makes the naming more similar to the way PL/pgSQL is organized. The initialization of the procedure caches was separated into a new function init_procedure_caches to keep the hash tables private to plpy_procedures.c. Jan Urbański and Peter Eisentraut 2011-12-18 14:14:16 -05:00			`typedef struct PLyResultObject`
			`{`
			`PyObject_HEAD`
			`/* HeapTuple tuples; /`
			`PyObject nrows; / number of rows returned by query */`
Run pgindent on 9.2 source tree in preparation for first 9.3 commit-fest. 2012-06-10 15:20:04 -04:00			`PyObject rows; / data rows, or empty list if no data`
			`* returned */`
Split plpython.c into smaller pieces This moves the code around from one huge file into hopefully logical and more manageable modules. For the most part, the code itself was not touched, except: PLy_function_handler and PLy_trigger_handler were renamed to PLy_exec_function and PLy_exec_trigger, because they were not actually handlers in the PL handler sense, and it makes the naming more similar to the way PL/pgSQL is organized. The initialization of the procedure caches was separated into a new function init_procedure_caches to keep the hash tables private to plpy_procedures.c. Jan Urbański and Peter Eisentraut 2011-12-18 14:14:16 -05:00			`PyObject status; / query status, SPI_OK_, or SPI_ERR_ */`
PL/Python: Add result metadata functions Add result object functions .colnames, .coltypes, .coltypmods to obtain information about the result column names and types, which was previously not possible in the PL/Python SPI interface. reviewed by Abhijit Menon-Sen 2012-01-30 14:38:52 -05:00			`TupleDesc tupdesc;`
Split plpython.c into smaller pieces This moves the code around from one huge file into hopefully logical and more manageable modules. For the most part, the code itself was not touched, except: PLy_function_handler and PLy_trigger_handler were renamed to PLy_exec_function and PLy_exec_trigger, because they were not actually handlers in the PL handler sense, and it makes the naming more similar to the way PL/pgSQL is organized. The initialization of the procedure caches was separated into a new function init_procedure_caches to keep the hash tables private to plpy_procedures.c. Jan Urbański and Peter Eisentraut 2011-12-18 14:14:16 -05:00			`} PLyResultObject;`

			`extern void PLy_result_init_type(void);`
			`extern PyObject *PLy_result_new(void);`

Run pgindent on 9.2 source tree in preparation for first 9.3 commit-fest. 2012-06-10 15:20:04 -04:00			`#endif /* PLPY_RESULTOBJECT_H */`