- 15 10月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 13 10月, 2005 1 次提交
-
-
由 Tom Lane 提交于
syntax checking to plpgsql: check_sql_expr() wasn't being called by make_select_stmt(), so that there was no SQL syntax check for SELECT statements.
-
- 04 10月, 2005 1 次提交
-
-
由 Tom Lane 提交于
Per buildfarm results and Michael Fuhr.
-
- 25 9月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 14 9月, 2005 2 次提交
- 25 8月, 2005 3 次提交
- 21 8月, 2005 1 次提交
-
-
由 Tom Lane 提交于
idea on consistency grounds, whether or not it really fixes bug #1831. Michael Fuhr
-
- 13 8月, 2005 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
FreeBSD ports, supplied by Jim C. Nasby
-
由 Bruce Momjian 提交于
> position. Performing the check in the existing position allows the call > to go through to perl first, possibly resulting in a SEGV. Andrew Dunstan
-
- 28 7月, 2005 2 次提交
-
-
由 Neil Conway 提交于
not ever write through the `isnull' parameter, it does not need to be an out parameter. Therefore it can be declared a "bool" rather than a "bool *".
-
由 Tom Lane 提交于
Per Kevin McArthur.
-
- 24 7月, 2005 1 次提交
-
-
由 Tom Lane 提交于
error message in Python 2.3 and before. Per Michael Fuhr and buildfarm results.
-
- 14 7月, 2005 1 次提交
-
-
由 Tom Lane 提交于
hack.
-
- 13 7月, 2005 1 次提交
-
-
由 Tom Lane 提交于
Reported by Michael Fuhr, fixed by Andrew Dunstan.
-
- 12 7月, 2005 1 次提交
-
-
由 Tom Lane 提交于
Add suitable regression tests. Andrew Dunstan
-
- 11 7月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
Add missing plperl include.
-
- 10 7月, 2005 3 次提交
-
-
由 Bruce Momjian 提交于
return arays nicely without having to make the plperl programmer aware of anything. The attached patch allows plperl to return an arrayref where the function returns an array type. It silently calls a perl function to stringify the array before passing it to the pg array parser. Non-array returns are handled as before (i.e. passed through this process) so it is backwards compatible. I will presently submit regression tests and docs. example: andrew=# create or replace function blah() returns text[][] language plperl as $$ return [['a"b','c,d'],['e\\f','g']]; $$; CREATE FUNCTION andrew=# select blah(); blah ----------------------------- {{"a\"b","c,d"},{"e\\f",g}} This would complete half of the TODO item: . Pass arrays natively instead of as text between plperl and postgres (The other half is translating pg array arguments to perl arrays - that will have to wait for 8.1). Some of this patch is adapted from a previously submitted patch from Sergej Sergeev. Both he and Abhijit Menon-Sen have looked it over briefly and tentatively said it looks ok. Andrew Dunstan
-
由 Bruce Momjian 提交于
for PL/Perl, to avoid loading the entire result set into memory as the existing spi_exec_query() function does. Here's how one might use the new functions: $x = spi_query("select ..."); while (defined ($y = spi_fetchrow($x))) { ... return_next(...); } The changes do not affect the spi_exec_query() interface in any way. Abhijit Menon-Sen
-
由 Bruce Momjian 提交于
when a plpython function returns unicode" thread: http://archives.postgresql.org/pgsql-bugs/2005-06/msg00105.php In several places PL/Python was calling PyObject_Str() and then PyString_AsString() without checking if the former had returned NULL to indicate an error. PyString_AsString() doesn't expect a NULL argument, so passing one causes a segmentation fault. This patch adds checks for NULL and raises errors via PLy_elog(), which prints details of the underlying Python exception. The patch also adds regression tests for these checks. All tests pass on my Solaris 9 box running HEAD and Python 2.4.1. In one place the patch doesn't call PLy_elog() because that could cause infinite recursion; see the comment I added. I'm not sure how to test that particular case or whether it's even possible to get an error there: the value that the code should check is the Python exception type, so I wonder if a NULL value "shouldn't happen." This patch converts NULL to "Unknown Exception" but I wonder if an Assert() would be appropriate. The patch is against HEAD but the same changes should be applied to earlier versions because they have the same problem. The patch might not apply cleanly against earlier versions -- will the committer take care of little differences or should I submit different versions of the patch? Michael Fuhr
-
- 07 7月, 2005 4 次提交
-
-
由 Bruce Momjian 提交于
Andrew Dunstan
-
由 Bruce Momjian 提交于
plperl - the attached small patch remedies that omission, and adds a small regression test for error and warning output - the new regression input and expected output are in separate attached files. Andrew Dunstan
-
由 Bruce Momjian 提交于
plperl - the attached small patch remedies that omission. Andrew Dunstan
-
由 Tom Lane 提交于
could not be reached before, but now that there is a plpgsql validator function, it can be. Check is needed to prevent core dump reported by Satoshi Nagayasu. Besides, this gives a more specific and useful error message for a fairly common novice error.
-
- 06 7月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
--------------------------------------------------------------------------- This patch allows the PL/Python module to do (SRF) functions. The patch was taken from the CVS version. I have modified the plpython.c file and have added a test sql script for testing the functionality. It was actually the script that was in the 8.0.3 version but have since been removed. In order to signal the end of a set, the called python function must simply return plpy.EndOfSet and the set would be returned. Gerrit van Dyk
-
- 05 7月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
The patch was taken from the CVS version. I have modified the plpython.c file and have added a test sql script for testing the functionality. It was actually the script that was in the 8.0.3 version but have since been removed. In order to signal the end of a set, the called python function must simply return plpy.EndOfSet and the set would be returned. Gerrit van Dyk
-
- 04 7月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 03 7月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
Improve code clarity by using macros for E'' processing.
-
- 02 7月, 2005 2 次提交
-
-
由 Neil Conway 提交于
end of the block: <<label>> begin ... end label; Similarly for loops. This is per PL/SQL. Update the documentation and add regression tests. Patch from Pavel Stehule, code review by Neil Conway.
-
由 Bruce Momjian 提交于
-
- 27 6月, 2005 2 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
with main, avoid using a SQL-defined SQLSTATE for what is most definitely not a SQL-compatible error condition, fix documentation omissions, adhere to message style guidelines, don't use two GUC_REPORT variables when one is sufficient. Nothing done about pg_dump issues.
-
- 23 6月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 22 6月, 2005 2 次提交
-
-
由 Neil Conway 提交于
we need to be careful to reset rc to PLPGSQL_RC_OK, depending on how the loop's logic is structured. If we continue a loop but it then exits without executing the loop's body again, we want to return PLPGSQL_RC_OK to our caller. Enhance the regression tests to catch this problem. Per report from Michael Fuhr.
-
由 Neil Conway 提交于
next iteration of a loop. Update documentation and add regression tests. Patch from Pavel Stehule, reviewed by Neil Conway.
-