[COMMITTERS] pgsql: Additional test coverage for boolean type (bool.c)

2008-10-05 Thread Peter Eisentraut
Log Message: --- Additional test coverage for boolean type (bool.c) Modified Files: -- pgsql/src/test/regress/sql: boolean.sql (r1.8 -> r1.9) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/boolean.sql?r1=1.8&r2=1.9) pgsql/src/test/

[COMMITTERS] pgsql: Additional test coverage for int8 type (int8.c)

2008-10-05 Thread Peter Eisentraut
Log Message: --- Additional test coverage for int8 type (int8.c) int8-exp-three-digits.out update untested, might need refinement. Modified Files: -- pgsql/src/test/regress/expected: int8-exp-three-digits.out (r1.9 -> r1.10) (http://anoncvs.postgresql.org/c

Re: [COMMITTERS] pgsql: Additional test coverage for int8 type (int8.c)

2008-10-05 Thread Tom Lane
[EMAIL PROTECTED] (Peter Eisentraut) writes: > Additional test coverage for int8 type (int8.c) > int8-exp-three-digits.out update untested, might need refinement. Either this patch or the bool one broke the buildfarm. regards, tom lane -- Sent via pgsql-committers mailin

[COMMITTERS] pgsql: Reverse int8.out and int8-exp-three-digits.out mixup.

2008-10-05 Thread Peter Eisentraut
Log Message: --- Reverse int8.out and int8-exp-three-digits.out mixup. Modified Files: -- pgsql/src/test/regress/expected: int8-exp-three-digits.out (r1.10 -> r1.11) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/int8-exp-three-di

[COMMITTERS] npgsql - Npgsql2: Changed tabs to spaces (4)

2008-10-05 Thread User Fxjr
Log Message: --- Changed tabs to spaces (4) Modified Files: -- Npgsql2/src/NpgsqlTypes: ArrayHandling.cs (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/NpgsqlTypes/ArrayHandling.cs.diff?r1=1.3&r2=1.4) -- Sent via pgsql-com

[COMMITTERS] pgsql: Remove obsolete internal functions istrue, isfalse, isnottrue,

2008-10-05 Thread Peter Eisentraut
Log Message: --- Remove obsolete internal functions istrue, isfalse, isnottrue, isnotfalse, nullvalue, nonvalue. A long time ago, these were used to implement the SQL constructs IS TRUE, etc. Modified Files: -- pgsql/src/backend/utils/adt: bool.c (r1.43 -> r1.44)

[COMMITTERS] npgsql - Npgsql2: [#1010488] NgsqlParameter of type containing DBNull

2008-10-05 Thread User Fxjr
Log Message: --- [#1010488] NgsqlParameter of type containing DBNull values throws NullReferenceException. Thanks Christ Akkermans for testcase. Now, Npgsql handles first elements which aren't null as Arrays and IEnumerables. Also added test case for this bug. Modified Files: -

[COMMITTERS] pgsql: Remove some unportable tests

2008-10-05 Thread Peter Eisentraut
Log Message: --- Remove some unportable tests Modified Files: -- pgsql/src/test/regress/expected: int8-exp-three-digits.out (r1.11 -> r1.12) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/int8-exp-three-digits.out?r1=1.11&r2=1.12)

[COMMITTERS] pgsql: Fix markTargetListOrigin() to not fail on a simple-Var reference

2008-10-05 Thread Tom Lane
Log Message: --- Fix markTargetListOrigin() to not fail on a simple-Var reference to a recursive CTE that we're still in progress of analyzing. Add a similar guard to the similar code in expandRecordVariable(), and tweak regression tests to cover this case. Per report from Dickson S. Gued

[COMMITTERS] pgsql: Improve behavior of WITH RECURSIVE with an untyped literal in the

2008-10-05 Thread Tom Lane
Log Message: --- Improve behavior of WITH RECURSIVE with an untyped literal in the non-recursive term. Per an example from Dickson S. Guedes. Modified Files: -- pgsql/src/backend/parser: parse_cte.c (r2.1 -> r2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/

[COMMITTERS] pgsql: Tweak the overflow checks in integer division functions to

2008-10-05 Thread Tom Lane
Log Message: --- Tweak the overflow checks in integer division functions to complain if the machine produces zero (rather than the more usual minimum-possible-integer) for the only possible overflow case. This has been seen to occur for at least some word widths on some hardware, and it's

[COMMITTERS] pgsql: Fix a missed case in int8-exp-three-digits.out, per buildfarm

2008-10-05 Thread Tom Lane
Log Message: --- Fix a missed case in int8-exp-three-digits.out, per buildfarm results. Modified Files: -- pgsql/src/test/regress/expected: int8-exp-three-digits.out (r1.12 -> r1.13) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/

[COMMITTERS] orafce - orafce: Fix out-of-range access in dbms_pipe.db_pipes.

2008-10-05 Thread User Itagaki
Log Message: --- Fix out-of-range access in dbms_pipe.db_pipes. Modified Files: -- orafce: pipe.c (r1.19 -> r1.20) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/pipe.c.diff?r1=1.19&r2=1.20) orafce/expected: orafunc.out (r1.11 -> r1.

[COMMITTERS] pgsql: Fix the implicit-RTE code to be able to handle implicit RTEs for

2008-10-05 Thread Tom Lane
Log Message: --- Fix the implicit-RTE code to be able to handle implicit RTEs for CTEs, as well as regular tables. Per discussion, this seems necessary to meet the principle of least astonishment. In passing, simplify the error messages in warnAutoRange(). Now that we have parser error p

[COMMITTERS] pgsql: Experimental patch to see if it fixes MSVC builds ...

2008-10-05 Thread Tom Lane
Log Message: --- Experimental patch to see if it fixes MSVC builds ... Modified Files: -- pgsql/src/tools/msvc: vcregress.pl (r1.7 -> r1.8) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/vcregress.pl?r1=1.7&r2=1.8) -- Sent via pgsql-commit

[COMMITTERS] npgsql - Npgsql2: removed dependencies on System.Web

2008-10-05 Thread User Jbcooley
Log Message: --- removed dependencies on System.Web Modified Files: -- Npgsql2/src: Npgsql2008.csproj (r1.15 -> r1.16) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql2008.csproj.diff?r1=1.15&r2=1.16) -- Sent via pgsql-committers mai

[COMMITTERS] npgsql - Npgsql2: updated to 2.0 for final release.

2008-10-05 Thread User Jbcooley
Log Message: --- updated to 2.0 for final release. Modified Files: -- Npgsql2/src/Npgsql: AssemblyInfo.cs (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/AssemblyInfo.cs.diff?r1=1.14&r2=1.15) -- Sent via pgsql-commi

[COMMITTERS] npgsql - Npgsql2: Updated for 2.0 release

2008-10-05 Thread User Jbcooley
Log Message: --- Updated for 2.0 release Modified Files: -- Npgsql2: ChangeLog (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/ChangeLog.diff?r1=1.8&r2=1.9) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.

[COMMITTERS] pgsql: Random speculation about the reason for PPC64 buildfarm failures:

2008-10-05 Thread Tom Lane
Log Message: --- Random speculation about the reason for PPC64 buildfarm failures: maybe isalnum is returning a value with the low-order byte all zero? Modified Files: -- pgsql/src/backend/utils/adt: formatting.c (r1.148 -> r1.149) (http://anoncvs.postgresq