This is an automated email from the git hooks/post-receive script.
ebourg-guest pushed a change to tag REL8_4_703
in repository libpostgresql-jdbc-java.
at 8f4050a (commit)
This tag includes the following new commits:
new 4824b5c Remove unused Sun specific import.
new 5b72e98 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 b75079d Add the new TRUNCATE privilege, that was added in 8.4, to
the list of known table privileges.
new cf625c7 When a COPY operation is the first statement issued in a
transaction, it was not sending the BEGIN necessary to start the transaction.
Refactor the non-query BEGIN code path used in fastpath calls to a common
function that copy can use as well.
new df9c12a Add the partial index constraint to the FILTER_CONDITION
column returned by DatabaseMetaData.getIndexInfo.
new 6b478e9 The 8.4 release added some code to avoid re-describing a
statement if we already had the type information available by copying the
resolved type information from the query to the parameters. Its goal was just
to overwrite parameters without a type (unknown), but it was actually
overwriting all types which could change the query's desired behavior.
new 19c3c04 Fix the ORDINAL_POSITION in the
DatabaseMetaData.getColumns. Previously we were returning simply
pg_attribute.attnum, but that doesn't work in the presence of dropped columns
because later columns don't get their attnum decremented if a preceding column
is dropped. Instead use the row_number window function for 8.4 and later
servers to figure out the live column position.
new c33a00b 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 3658328 First Japanese translation of error messages.
new 6d3d2e4 Initial Bulgarian translation.
new ed443d8 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 4eeb652 Protocol sync is lost when a batch statement parameter
has an embedded null byte. When the server responds with an error message, the
batch error handler tries to construct the equivalent original query text with
the parameters substituted in. This conversion fails on the driver side with
an IllegalArgumentException complaining about the null byte. There isn't a
catch block in place to handle that exception, so it returns all the way to the
user without processing [...]
new bc935cb Fix the previous fix for handling parameters with an
embedded null. The code was vulnerable to a NPE because it ignored the
carefully setup local variable for standardConformingStrings.
new ceafda2 Fix a problem using the Copy API to copy data to the
server from a Reader. After reading data out of the Reader and into a buffer,
we were sending the entire buffer on to the server, not just the subset of it
that was filled by the read operation.
new 482c77d 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 ae402c2 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 3643805 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 b515b16 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 22c9979 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 e8dff84 A previous test to ensure sane behavior in the presence
of null bytes didn't work for the V2 protocol because that error happens
earlier than in the V3 case.
new 72e9a57 Updated Japanese translation.
new 034baa3 Release 8.4-702.
new 957da71 Fix a minor concurrency issue during the setup for
processing escape functions.
new efc4cf7 Fix DatabaseMetaData.getColumns for 7.2 servers. The
change to use a window function to get the column position ended up breaking
the query for ancient servers.
new ce7dd6c Make ResultSetMetaData.getColumnType match the results of
DatabaseMetaData.getColumns.DATA_TYPE for domain and composite types.
new 72e9d33 Fix an array unit test when running with the V2 protocol.
With V2 we must provide the type information because it is not passed to the
server.
new c79d868 Work around a bug in the server's implementation of the
copy protocol. It returns command complete immediately upon receiving the EOF
marker in a binary copy, potentially before we've issued CopyDone/Fail. Fix
this by simply not processing the command complete message until we believe
that we are done with the copy as well.
new 85ba142 Handle a table with no permissions correctly.
new 154ca13 Make updatable ResultSets work with SQLXML data. Avoid
making the update code know about target types unless it needs to do some
special processing for it.
new 2fcd5ec If a domain has a not null constraint, report that
information in the metadata for both DatabaseMetaData.getColumns and
ResultSetMetaData.isNullable.
new 54ab771 In DatabaseMetaData.getSchemas, return the user's own
temp schemas, but no others. Previously it wasn't returning the users own temp
schema, but was showing all toast temp schemas.
new 3ac495c Update the date tests for changes in the 1.6 JVM. Older
versions allowed five digit years and single digit days and months. The latest
code only allows a strict yyyy-mm-dd. This changed somewhere between 1.6.0_11
and 1.6.0_21. Rumor has it that the Java7 code is again more flexible, but
Java6 isn't going away for a long time.
new a5a763b Allow the driver to support setObject with
Types.DISTINCT. We report metadata indicating that values are of this type, so
we'd better accept it coming back in.
new d21d365 Use slightly different SQL State error codes for the
different types of connection setup failures to indicate which can be retried
and which cannot.
new 3598626 Clear the generated keys associated with a Statement at
the next execution. If the next execution doesn't want generated keys, we
don't want to leave the old keys around.
new e3e4eb1 Fix getSchemas for 7.3 servers. 7.3 cannot extract an
array element from an array that is returned by a function. Instead coerce it
to text and pull it out with a regex.
new 8f4050a Change version to 8.4-703 for release.
The 37 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
