Log Message:
Update databases/jdbc-postgresql81 from 408 to 411

Version 8.1-411 (2007-12-02)

  * fix When doing batch execution we can have multiple Parse
    and DescribeStatement messages on the wire at the same time.
    When we finally get around to collecting the DescribeStatement
    results we must check whether they still apply to the currently
    parsed query. Otherwise we'll overwrite our type information
    with stale data that will cause failures down the line. (jurka)
    Thanks to Eric Faulhaber.
  * fix CallableStatements with OUT parameters that get executed
    more than prepareThreshold times failed if clearParameters()
    was called in between executions. When we've hit the
    prepareThreshold, we no longer send Parse messages which invoke
    SimpleParameterList.getTypeOID which has side effects required
    to setup the parameters correctly. Add an explicit
    convertFunctionOutParameters method to do this work instead
    that we call in all execution paths. (jurka) Thanks to Ludovico
    Bianchini.
  * fix Multiple calls to XAConnection.getConnection within the
    same user transaction ended up restarting the transaction on
    the server side as a result of manipulating the autocommit
    state. When retrieving a Connection, we must pay attention to
    whether a user transaction is in progress when setting the
    autocommit state. (jurka) Thanks to Heikki Linnakangas.
  * fix Make code that parses queries for updateable resultsets
    aware of the ONLY clause. (jurka) Thanks to Oleg Vasylenko.
  * fix While custom type maps are not implemented, the code to
    detect the caller trying to use them threw a ClassCastException.
    Correctly detect the attempted use of custom types and bail
    out with a SQLException. (jurka)

Version 8.1-410 (2007-07-31)

  * add Make setObject recognize a parameter of type java.lang.Byte.
    (jurka) Thanks to Boom Roos.
  * fix Updatable ResultSets did not work when updating bytea
    data and then retrieving it because we send the data to the
    server in binary format, but the ResultSet was expecting to
    read it in text format. So we need to convert the data from
    binary to text format before stuffing it into the ResultSet.
    (jurka) Thanks to Mikko Tiihonen.
  * fix Do escape processing on batch Statements prior to execution.
    This already worked for PreparedStatements, but not plain
    Statements. (jurka) Thanks to Hui Ye.
  * fix Don't return quotes around identifiers in the results of
    DatabaseMetaData.getIndexInfo even if they would require quoting
    in SQL. (jurka) Thanks to Andrei Badea.
  * fix When retrieving the columns of a function that returns
    a complex type, don't retrieve system columns (like xmin/xmax/...)
    that you'll find if the type is from a table. (jurka)
  * fix The previous fix to try and set a XA based Connection's
    autocommit property correctly didn't quite work. Calling
    XAConnection.getConnection set autocommit to true even if we
    already had a transaction in progress. (jurka) Thanks to Luca
    Ferrari, Heikki Linnakangas.
  * fix Error message was reporting the wrong parameter type
    value in the V3 protocol's SimpleParameterList implementation.
    (jurka) Thanks to Nathan Keynes.
  * fix Backpatch fix to 8.1: Allow XAResource.start with TMJOIN
    in a limited set of circumstances to work with WebLogic. We
    allow TMJOIN only if the resource was previously ended and the
    Xid is the same as the current Xid. (jurka) Thanks to Jan de
    Visser and Heikki Linnakangas.
  * fix Backpatch fix to 8.1: A XAConnections default autocommit
    state should be true. The driver was previously setting autocommit
    to false and assuming it would stay that way. This caused two
    problems. First, some applications expected to be able to issue
    local autocommit transactions prior to begin(). Second, some
    TMs (Geronimo) set the autocommit state to true themselves,
    which causes problems as the driver did not expect it to be
    changed. This patch correctly disables and enables autocommit
    around begin, prepare, commit, and rollback methods. (jurka)
    Thanks to Allan Saddi.
  * fix Explicitly state which source level we are compiling.
    Newer versions of gij/gcj run a 1.5 VM, but default to a 1.4
    source level compile which tricks up our build system. This
    still doens't fix the case of running with a newer VM than
    compiler, but I don't see what we can do about that. (jurka)
    Thanks to Tom Lane, Oliver Jowett.

Version 8.1-409 (2007-04-18)

  * add Implement ResultSet.updateArray by simply mapping it to
    updateObject which now works for arrays. (jurka)
  * fix Statement.getTime, .getDate, and .getTimestamp methods
    which are passed a Calendar object were rotating the timezone
    in the wrong direction. Rewrite this code to use the existing
    TimestampUtils methods to match the working code in ResultSets.
    (jurka) Thanks to Ravi Periasmy.
  * fix Produce the timezone that we send to the server in the
    same format that we can parse. This is important for updatable
    ResultSets as we must be able to parse the format we produce.
    (jurka) Thanks to Leon Do.
  * fix Fix persistence of XA datasources. PGObjectFactory wasn't
    aware of PGXADataSource and can't be because of the requirements
    for different build versions. Add a new PGXADataSourceFactory
    to provide this functionality. (jurka) Thanks to Heikki
    Linnakangas.
  * fix Fix the error message generated by a CallableStatement
    not getting results that match the registered out parameters
    to report the correct parameter position. (jurka)
  * fix Interval formatting didn't work for negative seconds
    values greater than -1. It would format it as -.5, but interval
    input doesn't accept this, so write it as -0.5 instead. (jurka)
  * fix Allow updatable ResultSets to update arrays. (jurka)
    Thanks to Vasylenko.
  * fix In an error message reporting an unparseable timestamp
    value the code was trying to put the unparseable portion into
    the error message, but used the wrong variable to get the
    correct length. (jurka)