[libpostgresql-jdbc-java] tag REL8_3_606 created (now 5e1cb76)
Emmanuel Bourg
ebourg-guest at moszumanska.debian.org
Mon Jan 9 10:20:47 UTC 2017
This is an automated email from the git hooks/post-receive script.
ebourg-guest pushed a change to tag REL8_3_606
in repository libpostgresql-jdbc-java.
at 5e1cb76 (commit)
This tag includes the following new commits:
new 997746c Make the build system aware of the 1.7 JDK (which icedtea reports itself as) and add an explicit check and complaint if we find a JDK that we don't support.
new db9277b Move PGXADataSource to the public API documentation.
new 1cdaa3f Do comparison of identifiers in a known Locale (specificially US). In Turkish for example "id".toLowerCase().equals("ID".toLowerCase()) is false. This breaks apps running a Turkish locale.
new dc8fe8f Fix a deadlock that occurs when retrieving notifications. Normal query execution enters the QueryExecutor monitor and then calls a synchronized method in the ProtocolConnection to update the transaction state. Notification retrieval operates in the reverse order, entering the ProtocolConnection monitor and then calling a synchronized method in the QueryExecutor.
new 3c303dc CallableStatement#getUpdateCount was returning 1 when a function returned a ResultSet. Return -1 instead.
new 6efa10b The DataSource options for ssl where not correctly being serialized or included in the Reference.
new ca13012 Accept UTF8 as an equivalent of UNICODE when trying to detect if client_encoding has changed to something the driver doesn't understand. Don't try to accept every possible spelling (UTF-8) as UTF8 is the server's canonical name and people shouldn't be messing with this anyway.
new 49e3580 Updated German translation.
new a1999da 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.
new 33e795c DatabaseMetaData.getTypeInfo was reporting whether the type was signed or not, but the output column is really supposed to indicate whether the the type is unsigned or not.
new 7a84f8a Support a parameter (?) for the amount part of the timestampadd function. Previously we only supported literals.
new f8e3280 Release build 8.3-604.
new 7882989 The Statement and Connection proxies used for connection pooling code relied on the underlying real connection and statement code for equals and hashcode support. When the proxies are closed we discard the references to the real objects, so we can't rely on them for this support because we'll get a NullPointerException.
new 0c4b197 My previous patch to fix the equals and hashcode for connection pools didn't build with a 1.4 JDK. 1.5+ was doing autoboxing which I didn't originally notice.
new db2cbc7 Typo: Types.Other -> Types.OTHER.
new 24b0dac The commit extending support for DBMD.getColumns to include JDBC 3 and 4 specific results was busted for 7.2 servers. Need to join to pg_type.
new a027641 Don't use pg_attrdef.adsrc to display a column's default value. This can get out of date when dependent objects are renamed. Instead decompile the adbin column to fetch up to date information.
new a7bd7b8 Fix sign handling for getFastXXX methods. Don't allow '-' or '-.'.
new 7f5b82b Initialize BatchUpdateExceptions with the SQLState of the SQLException that they are wrapping. Code that inspects the SQLStates of SQLExceptions, but doesn't unwrap the nested exception will not understand the underlying cause and may make incorrect decisions about the severity of the error.
new d6653a1 Fix time tests for timezones which have different rules now than at the unix epoch. We need to pull the zone offset for the time value we're manipulating rather than the current time. "Europe/London" is the failing example, but there may be more.
new 577936d Release 8.3-605.
new ea835a4 After running the statement passed to executeUpdate, we check to see if it was a SELECT and complain because it is not a query method. The code was not checking all of the results if it was passed a multi- statement query string. This resulted in the surprising and silent partial execution of SELECT statements.
new aa76803 Always specify an XA error code when creating an XAException. Otherwise a transaction manager won't know what to do with the error and may have to asssume the worst.
new 05c0240 LOB truncation didn't allow truncating to zero length because it was improperly using the positioning length checks which don't allow a zero length.
new 3844134 A XA transaction should not change the autocommit setting of a Connection. Ensure that we restore this property correctly after the XA transaction completes.
new 1bdc95f PoolingDataSources were not picking up all of the properties that were set for them. Notably it would not give you a SSL connection when asked. It was copying individual properties over piecemeal and this got out of date as new properties were added to the BaseDataSource, but not added to the copying code. Use the existing serialization code to ensure that we really do copy all of the properties over.
new 1b29b12 When setNull is called with a TIME or TIMESTAMP type we cannot pass that type information on to the backend because we really don't know whether it is with or without a time zone. For a NULL value it doesn't matter, but we can't establish a type because a later call with a non-null value using the same PreparedStatement can potentially end up using a specific type that is incorrect.
new 107765c Add some more specific types to the return value for DatabaseMetaData.getTables. Return composite types, temporary views, and temporary sequences with TABLE_TYPE values specifically for them.
new 93c095e Fix up the previous patch to ensure datasource parameters are set properly. We must close the ObjectOutputStream to flush the data to the byte array.
new 5e1cb76 Release 8.3-606.
The 30 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/libpostgresql-jdbc-java.git
More information about the pkg-java-commits
mailing list