From jurka at pgfoundry.org Wed Oct 8 18:24:06 2008 From: jurka at pgfoundry.org (User Jurka) Date: Wed, 8 Oct 2008 18:24:06 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Implement support for SQLXML. Message-ID: <20081008182406.4D83817ADE2B@pgfoundry.org> Log Message: ----------- Implement support for SQLXML. All of the underlying XML tools don't seem to support handling fragments, but these are allowed in the server xml type. I'm also not sure there aren't any encoding problems, but it mostly seems to work. Modified Files: -------------- pgjdbc: build.xml (r1.82 -> r1.83) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/build.xml.diff?r1=1.82&r2=1.83) pgjdbc/org/postgresql: Driver.java.in (r1.75 -> r1.76) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/Driver.java.in.diff?r1=1.75&r2=1.76) pgjdbc/org/postgresql/core: Oid.java (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/core/Oid.java.diff?r1=1.14&r2=1.15) TypeInfo.java (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/core/TypeInfo.java.diff?r1=1.2&r2=1.3) pgjdbc/org/postgresql/jdbc2: TypeInfoCache.java (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc2/TypeInfoCache.java.diff?r1=1.16&r2=1.17) pgjdbc/org/postgresql/jdbc3g: AbstractJdbc3gStatement.java (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc3g/AbstractJdbc3gStatement.java.diff?r1=1.1&r2=1.2) Jdbc3gConnection.java (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc3g/Jdbc3gConnection.java.diff?r1=1.5&r2=1.6) pgjdbc/org/postgresql/jdbc4: AbstractJdbc4Connection.java (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc4/AbstractJdbc4Connection.java.diff?r1=1.6&r2=1.7) AbstractJdbc4ResultSet.java (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc4/AbstractJdbc4ResultSet.java.diff?r1=1.5&r2=1.6) AbstractJdbc4Statement.java (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc4/AbstractJdbc4Statement.java.diff?r1=1.4&r2=1.5) pgjdbc/org/postgresql/test/jdbc4: Jdbc4TestSuite.java (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/test/jdbc4/Jdbc4TestSuite.java.diff?r1=1.6&r2=1.7) UUIDTest.java (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/test/jdbc4/UUIDTest.java.diff?r1=1.1&r2=1.2) Added Files: ----------- pgjdbc/org/postgresql/jdbc3g: AbstractJdbc3gConnection.java (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc3g/AbstractJdbc3gConnection.java?rev=1.1&content-type=text/x-cvsweb-markup) pgjdbc/org/postgresql/jdbc4: Jdbc4SQLXML.java (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/jdbc4/Jdbc4SQLXML.java?rev=1.1&content-type=text/x-cvsweb-markup) pgjdbc/org/postgresql/test/jdbc4: XmlTest.java (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/test/jdbc4/XmlTest.java?rev=1.1&content-type=text/x-cvsweb-markup) From jurka at pgfoundry.org Wed Oct 8 18:25:33 2008 From: jurka at pgfoundry.org (User Jurka) Date: Wed, 8 Oct 2008 18:25:33 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: I had commented out the non-JDBC4 tests to speed up testing of Message-ID: <20081008182533.77AAF17ADE0D@pgfoundry.org> Log Message: ----------- I had commented out the non-JDBC4 tests to speed up testing of SQLXML work. Put back the testing of everything. Modified Files: -------------- pgjdbc: build.xml (r1.83 -> r1.84) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/build.xml.diff?r1=1.83&r2=1.84) From jurka at pgfoundry.org Wed Oct 8 18:43:51 2008 From: jurka at pgfoundry.org (User Jurka) Date: Wed, 8 Oct 2008 18:43:51 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Don't bother running the SQLXML tests against a server that Message-ID: <20081008184351.8E19717ADE27@pgfoundry.org> Log Message: ----------- Don't bother running the SQLXML tests against a server that wasn't built --with-libxml. Modified Files: -------------- pgjdbc/org/postgresql/test/jdbc4: Jdbc4TestSuite.java (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/test/jdbc4/Jdbc4TestSuite.java.diff?r1=1.7&r2=1.8) From jurka at pgfoundry.org Sat Oct 18 13:40:33 2008 From: jurka at pgfoundry.org (User Jurka) Date: Sat, 18 Oct 2008 13:40:33 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Adjust the deadlock avoidance code for the V3 protocol to be Message-ID: <20081018134033.C32B317ADE12@pgfoundry.org> Log Message: ----------- Adjust the deadlock avoidance code for the V3 protocol to be concerned with many statements in a single execute call in addition to the existing worry about many statements from an executeBatch call. This doesn't prevent all possible deadlocks as the deadlock avoidance calculation was written for batch execution which should not be returning ResultSets. If many long queries that return significant results are issued with a single execute we will still deadlock. Modified Files: -------------- pgjdbc/org/postgresql/core/v3: QueryExecutorImpl.java (r1.41 -> r1.42) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/core/v3/QueryExecutorImpl.java.diff?r1=1.41&r2=1.42) From jurka at pgfoundry.org Sat Oct 18 13:40:41 2008 From: jurka at pgfoundry.org (User Jurka) Date: Sat, 18 Oct 2008 13:40:41 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Adjust the deadlock avoidance code for the V3 protocol to be Message-ID: <20081018134041.17DE017ADE1C@pgfoundry.org> Log Message: ----------- Adjust the deadlock avoidance code for the V3 protocol to be concerned with many statements in a single execute call in addition to the existing worry about many statements from an executeBatch call. This doesn't prevent all possible deadlocks as the deadlock avoidance calculation was written for batch execution which should not be returning ResultSets. If many long queries that return significant results are issued with a single execute we will still deadlock. Tags: ---- REL8_3_STABLE Modified Files: -------------- pgjdbc/org/postgresql/core/v3: QueryExecutorImpl.java (r1.39.2.1 -> r1.39.2.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/core/v3/QueryExecutorImpl.java.diff?r1=1.39.2.1&r2=1.39.2.2) From jurka at pgfoundry.org Sat Oct 18 13:40:49 2008 From: jurka at pgfoundry.org (User Jurka) Date: Sat, 18 Oct 2008 13:40:49 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Adjust the deadlock avoidance code for the V3 protocol to be Message-ID: <20081018134049.30CE817ADE12@pgfoundry.org> Log Message: ----------- Adjust the deadlock avoidance code for the V3 protocol to be concerned with many statements in a single execute call in addition to the existing worry about many statements from an executeBatch call. This doesn't prevent all possible deadlocks as the deadlock avoidance calculation was written for batch execution which should not be returning ResultSets. If many long queries that return significant results are issued with a single execute we will still deadlock. Tags: ---- REL8_2_STABLE Modified Files: -------------- pgjdbc/org/postgresql/core/v3: QueryExecutorImpl.java (r1.33.2.4 -> r1.33.2.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/core/v3/QueryExecutorImpl.java.diff?r1=1.33.2.4&r2=1.33.2.5) From jurka at pgfoundry.org Sat Oct 18 13:40:57 2008 From: jurka at pgfoundry.org (User Jurka) Date: Sat, 18 Oct 2008 13:40:57 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Adjust the deadlock avoidance code for the V3 protocol to be Message-ID: <20081018134057.3582917ADE1C@pgfoundry.org> Log Message: ----------- Adjust the deadlock avoidance code for the V3 protocol to be concerned with many statements in a single execute call in addition to the existing worry about many statements from an executeBatch call. This doesn't prevent all possible deadlocks as the deadlock avoidance calculation was written for batch execution which should not be returning ResultSets. If many long queries that return significant results are issued with a single execute we will still deadlock. Tags: ---- REL8_1_STABLE Modified Files: -------------- pgjdbc/org/postgresql/core/v3: QueryExecutorImpl.java (r1.25.2.8 -> r1.25.2.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/core/v3/QueryExecutorImpl.java.diff?r1=1.25.2.8&r2=1.25.2.9) From jurka at pgfoundry.org Sat Oct 18 13:41:06 2008 From: jurka at pgfoundry.org (User Jurka) Date: Sat, 18 Oct 2008 13:41:06 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Adjust the deadlock avoidance code for the V3 protocol to be Message-ID: <20081018134106.0C41C17ADE21@pgfoundry.org> Log Message: ----------- Adjust the deadlock avoidance code for the V3 protocol to be concerned with many statements in a single execute call in addition to the existing worry about many statements from an executeBatch call. This doesn't prevent all possible deadlocks as the deadlock avoidance calculation was written for batch execution which should not be returning ResultSets. If many long queries that return significant results are issued with a single execute we will still deadlock. Tags: ---- REL8_0_STABLE Modified Files: -------------- pgjdbc/org/postgresql/core/v3: QueryExecutorImpl.java (r1.21.2.7 -> r1.21.2.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/core/v3/QueryExecutorImpl.java.diff?r1=1.21.2.7&r2=1.21.2.8) From jurka at pgfoundry.org Sun Oct 19 19:52:35 2008 From: jurka at pgfoundry.org (User Jurka) Date: Sun, 19 Oct 2008 19:52:35 +0000 (UTC) Subject: [Jdbc-commits] pgjdbc: Add tests to make sure that we can handle infinite dates that Message-ID: <20081019195235.2063217ADE15@pgfoundry.org> Log Message: ----------- Add tests to make sure that we can handle infinite dates that are now supported in 8.4. Modified Files: -------------- pgjdbc/org/postgresql/test/jdbc2: TimestampTest.java (r1.22 -> r1.23) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/test/jdbc2/TimestampTest.java.diff?r1=1.22&r2=1.23)