Up to [cvs.NetBSD.org] / pkgsrc / databases / jdbc-postgresql81
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Retire PostgreSQL 8.1.
Use INSTALLATION_DIRS
Updated databases/jdbc-postgresql81 to 412 # Updated Brazilian Portuguese translation. (jurka) Thanks to Euler Taveira de Oliveira. # fix While the driver currently doesn't support the copy protocol, it needs to understand it enough to ignore it. Now the connection will not be irreparably broken when a COPY request is sent. (jurka) Thanks to Altaf Malik. # fix The JDBC spec says that when you have two duplicately named columns in a ResultSet, a search by name should return the first one. Previously our code was returning the second match. (jurka) Thanks to Magne Mahre.
Mechanical changes to add DESTDIR support to packages that install their files via a custom do-install target.
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)
Whitespace cleanup, courtesy of pkglint. Patch provided by Sergey Svishchev in private mail.
Updated databases/jdbc-postgresql81 to 8.1-480: Version 8.1-408 (2006-12-01) * update Italian translation update. (jurka) Thanks to Giuseppe Sacco. * 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 error message in CallableStatement to identify the mismatch with the registered return type. (jurka) * fix Correct escaping of named savepoints which follow identifier, not literal rules. (jurka) Thanks to Michael Paesold. Version 8.1-407 (2006-05-23) * update Remove documentation's claim that we don't support functions with out parameters. (jurka) * update Updated German translation. (jurka) Thanks to Andre Bialojahn. * fix 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. (jurka) * fix When running against a 8.1+ server with protocol version 2 we cannot handle output parameters and can only handle the traditional function return value. (jurka) Version 8.1-406 (2006-05-22) * update Updated German transalation. (jurka) Thanks to Andre Bialojahn. * fix 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. Also with a function that has an in parameter and an out parameter, the out parameter will be registered at position 2, but will be returned in a result at position 1 because the first input parameter generates no output. The driver needs to correctly map between these two parameter offsets. (davec) Thanks to Luis Londono. * 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 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. (jurka) Thanks to Till Toenges. * 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 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. (jurka) Thanks to Oliver Jowett. * 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. * fix 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. (jurka) Thanks to Niels Beekman.
Set USE_JAVA=run because this package needs JRE only.
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)
Recursive revision bump / recommended bump for gettext ABI change.
Import jdbc-postgresql81 into pkgsrc: This is a pure Java (Type IV) JDBC driver for the PostgreSQL database. It allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The driver provides a reasonably complete implementation of the JDBC 3 specification in addition to some PostgreSQL specific extensions.
Initial revision