This is an automated email from the git hooks/post-receive script.
ebourg-guest pushed a change to tag REL8_1_408
in repository libpostgresql-jdbc-java.
at db52e0e (commit)
This tag includes the following new commits:
new c910ef2 Correct the display size calculations for numeric data.
Don't add precision and scale because scale is just a subset of precision.
new 9604d6d DatabaseMetaData.getTables should return all table type
if passed null as for the types array. It was previously returning only those
tables that psql's \d command would for a null type filter.
new 5eaa49b Remove javadoc @see reference pointing to removed
functionality.
new b2731e4 Statement.cancel was prone to race conditions even with a
single threaded client. It would fire off a cancel message without waiting for
an acknowledgement of its success. This resulted in future queries being
cancelled when the cancel message was received by the backend. Ensure we get
an EOF from the server before returning from the cancel call. This
still does nothing about multi-threaded race conditions.
new 5c996c3 Add scale information for time/timestamp/interval to
DatabaseMetaData.getColumns. Include knowledge of interval in
ResultSetMetaData.
new 77f5e30 Updated Italian translation from Giuseppe Sacco.
new f367d8d Update getObject and getArray methods that take a map to
only bail out with a not implemented exception if the supplied map is not null
and not empty. Apparently Sun's WebRowSet implementation passes empty Maps to
these methods.
new 407dbbe The V2 protocol wasn't correctly handling EmptyQuery
messages. It expected a four byte message length after the EmptyQuery message,
but there is only a single null byte sent by the backend.
new f74b674 Backpatch the fix for incorrect parameter indexes on
CallableStatements that do not return values to 8.1
new 64cf8e5 Brazilian Portuguese translation updates.
new 32fe073 When performing replace processing we must continue
processing until we hit the end of a user supplied query, not just once we've
detected the end of a valid query. Consider the example: SELECT a FROM t WHERE
(1>0)) ORDER BY a; We must send the whole query to the backend, not just the
section before the last closing parenthesis.
new d9b3c67 escapeQuotes() in DatabaseMetaData was not correctly
handling backslashes which would result in incorrect searches and has the
potential for a SQL injection attack.
new 60ae42a The TypeInfoCache had a static Map for the pg type name
to java.sql.Types conversion, but it was being reinitialized for each new
Connection. Even though its content is static make this an instance variable
for simplicity.
new 5dbd05a Release build 405.
new 4ad1445 When the Connection retrieved from
XAConnection.getConnection() is closed we do not want to rollback the
transaction because the underlying connection is not closed and the transaction
is being managed by the XAResource, not the Connection.
new 3d46f25 When a prepared statement uses different parameter types
than what the statement was originally prepared for, the driver must replan the
query for the new types. When doing this in batches the driver was not
correctly freeing old plans.
new dd554e3 When performing replace processing we must continue
processing until we hit the end of a user supplied query, not just once we've
detected the end of a valid query. Consider the example: SELECT a FROM t WHERE
(1>0)) ORDER BY a; We must send the whole query to the backend, not just the
section before the last closing parenthesis.
new 9acc6d6 gij/gcj has some JDK1.5 classes in it, but it only
supports JDK1.4 as the default source level. This confuses older ant versions
and our build script tries to compile a JDK1.5 version. Instead of letting ant
detect the java version, let the jvm tell us that itself using
java.specification.version as suggested by Heikki Linnakangas. Also put in a
check for a JDK1.6 compile attempt and bail out with an explanatory unsupported
error message instead of just failing at [...]
new b5f7e9a When we're unable to parse a timestamp value, the error
message should print out the bad value. It was printing a char array which
showed up as a useless [C@xxxx.
new f03d154 The previous commit message is completely bogus. I use
the -F argument to specify a filename and I picked com.msg instead of oom.msg
resulting in a random old message. This is the correct log entry.
new 7ba14af Add some more synchronization to the TypeInfoCache. We
need synchronization around the PreparedStatements because they may not be used
by two threads at the same time. Additional synchronization is applied to the
maps to ensure that they are in sync with each other. Make _pgNameToSQLType
static.
new 9d967ba Updated German transalation.
new 3695bbf Error messages were not run through MessageFormat if it
didn't have any parameters. This was a problem because all error messages are
written expecting to be run through the formatter and use two single quotes
when only one is desired in the output. Without being run through the
formatter the two quotes appeared in the output.
new 75d2560 Fix a couple of bugs in CallableStatement outputs. An
oversight in the checking of actual results vs. what the caller specified for
registerOutParameter was checking all register parameters against the first out
parameter, not the parameter it actually corresponded with.
new 6b08294 Release build 406.
new 5aaa290 Remove documentation's claim that we don't support
functions with out parameters.
new 03e92ab Updated German transalation.
new 982b94c Backpatch fix for running callable statements against a
8.1+ server with the v2 protocol. In this case we can't handle out parameters
and fallback to traditional processing.
new b60938e Using callable statements against older server versions
(7.4 or 8.0) did not work because of recent changes to output parameter
handling. 7.4 and 8.0 do not support function output parameters, but they still
must support the functions return value. Every function must have either a
return value or an output parameter so we force the minimum output parameter
count to one.
new d9e844e Release build 8.1-407.
new bdfcd57 Updated Italian translation from Giuseppe Sacco.
new b1bbfeb Brazilian Portuguese translation updates.
new fdf4f16 When issuing multiple queries on one statement the driver
was not clearing some intermediate state between executions. When an update,
insert, or delete followed a select, the select's results were still available
and would be returned instead of the non-query's affected row count.
new 6224384 When the driver asks the server to resolve a type the
resolved type is stored in the SimpleQuery object. When the statement is
executed again the driver determines whether the existing types match or if it
needs to be reprepared by comparing the current Statement's settings with the
SimpleQuery. The Statement will have the unspecified oid while the SimpleQuery
will have the resolved oid, so there will not be a match and the statement will
needlessly be reprepared. [...]
new a24b7a4 When creating a ResultSet from a refcursor, respect the
creating ResultSet's scollability setting. The way the ResultSet is created
means that it will always be scrollable anyway, so there's no downside. We
cannot support updatable refcursor ResultSets until we get updatable cursors.
new 08eb129 Fix a bug in function escape processing. When dealing
with an invalid escape the code attempted to read until it hit the escape end
and press on, but it forgot to increment its position counter. This lead to an
infinite loop that eventually resulted in an out of memory error.
new a91bc52 Update the documentation to reflect the fact that the
default prepareThreshold is five, not zero.
new e68e7df Error message wants the paramter's registered return
type, not the whole array of return types that will be displayed as something
unintelligible.
new 7e5c4ca RecoverdXid.equals was assuming that the object passed to
it was an Xid which in the general case of the equals method is not true. To
respect the contract of the equals method return false if the passed in object
isn't an Xid.
new ef74f71 Escaping of savepoint names in
org.postgresql.jdbc3.PSQLSavepoint is incorrect. Backslashes in (double-quoted)
savepoint names are doubled for escaping, but AFAIK, and as my testing shows,
savepoint names are like identifiers, so regular identifier quoting applies to
them.
new db52e0e Release 8.1-408.
The 41 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
_______________________________________________
pkg-java-commits mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-commits
