Log message:
Remove PostgreSQL 8.0.

Log message:
Mechanical changes to add DESTDIR support to packages that install
their files via a custom do-install target.

Log message:
Update databases/jdbc-postgresql80 from 318 to 321

Version 8.0-321 (2007-12-02)

  * 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.0-320 (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 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 Error message was reporting the wrong parameter type
    value in the V3 protocol's SimpleParameterList implementation.
    (jurka) Thanks to Nathan Keynes.
  * 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.0-319 (2007-04-18)

  * add Implement ResultSet.updateArray by simply mapping it to
    updateObject which now works for arrays. (jurka)
  * 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 Allow updatable ResultSets to update arrays. (jurka)
    Thanks to Vasylenko.

Log message:
Whitespace cleanup, courtesy of pkglint.
Patch provided by Sergey Svishchev in private mail.

Log message:
Update databases/jdbc-postgres80 from postgresql-jdbc-8.0-315 to 318

Version 8.0-318 (2006-12-01)

  * update Brazilian Portuguese translation update. (jurka) Thanks
    to Euler Taveira de Oliveira.
  * fix 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. (jurka) Thanks to Gilles
    Rayrat.
  * fix 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. Allow an unspecified
    oid to match any resolved type. (jurka) Thanks to Akira Sato.
  * fix 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. (jurka)
  * fix 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. (jurka)
  * fix Update the documentation to reflect the fact that the
    default prepareThreshold is five, not zero. (jurka)
  * fix Correct escaping of named savepoints which follow
    identifier, not literal rules. (jurka) Thanks to Michael Paesold.

Version 8.0-317 (2006-05-23)

  * fix A bad merge of out of memory detection and zero testing
    resulted in incorrectly handing of null values. (jurka) Thanks
    to Glenn Holmer.

Version 8.0-316 (2006-05-22)

  * fix 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. (jurka) Thanks to Giuseppe Sacco.
  * fix An OutOfMemoryError during fe<->be communication leaves
    the protocol in an unknown state. This prevents the caller from
    even closing the connection. Checking every allocation is a
    lot of work, but the most likely error location is going to be
    when receiving large result sets. Put in checks around receiving
    row data to detect memory exhaustion, keep the protocol in a
    known state, and report the failure back to the user. (jurka)
    Thanks to David Blasby.
  * fix 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 some random point. (jurka)
  * fix 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. To
    cleanup prepared statements the driver records a reference to
    a query object in response to the ParseComplete message. The
    problem in this case was that since the driver sends multiple
    Parse messages before a Sync, when the driver receives the
    first ParseComplete message the query object now contains a
    reference to the latest parsed statement, not the first. So it
    was only cleaning up the last parsed statement not all of them.
    (jurka) Thanks to Peter Eisentraut.

Log message:
Set USE_JAVA=run because this package needs JRE only.

Log message:
Updated jdbc-postgresql74 to 216
Updated jdbc-postgresql80 to 315
Updated jdbc-postgresql81 to 405
	No change logs found.

Removed jdbc-postgresql (has been re-imported as jdbc-postgresql73)

Log message:
Recursive revision bump / recommended bump for gettext ABI change.