2
I Use This!
Moderate Activity

Commits : Listings

Analyzed 5 days ago. based on code collected 5 days ago.
Jun 11, 2023 — Jun 11, 2024
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Fix a dumb cut and paste error from my last commit and update some of the jdbc3 metadata responses More... over 21 years ago
Fixed bug reported by Marko Strukelj and Keith Wannamaker. Using executeBatch on a preparedStatement would reset the prepared statment causing subsequent uses of the preparedStatement to fail (i.e. the following series of calls would fail: addBatch() executeBatch() addBatch() executBatch()). This is a regression from 7.2 where this worked correctly. The regression test has also been modified to explicitly test for this case. More... over 21 years ago
Applied patch submitted by Mats Lofkvist fixing serious threading problem introduced in beta3. Fixed bug with using setNull()(or setXXX(x, null)) and serverside prepare statements. Improved error message when using a connection object that has already been closed. More... over 21 years ago
Fixes bug where join to pg_description was incorrect. Also modifies the regression test to test for this case. Patch submitted by Kris Jurka. More... over 21 years ago
Applied two patches from Kris Jurka. - First fixes a problem with a recent patch allowing setNull on updateable resultsets - Second removed toLower() calls on database object names. Leave it to the caller to correctly pass lower, upper or mixed case. The driver already has methods that the caller can use to determine that postgres stores identifiers in lowercase. (unless the identifier was quoted when created). More... over 21 years ago
Return something meaningful for Statement.getFetchSize(). Previously we were returning an exception when this method was called. More... over 21 years ago
Patch submitted by Kris Jurka to fix arrayindexoutofbounds exception caused by improper array initialization. More... over 21 years ago
Applied patch from Teofilis Martisius to improve performance. Also removed some unused files and fixed the which needed a small change after the previous patch to build.xml. More... over 21 years ago
Applied patch submitted by Mike Beachy to give a better error message if configure hasn't been run before trying to build. Also cleaned up the README file and removed some obsolete files. More... over 21 years ago
Applied patch submitted by Kris Jurka to result in a better error message under some circumstances and handle negative money values better. More... over 21 years ago
Backed out part of the change from 1.6. The attempt to support int8 binds in such a way that indexes on int8 columns would be used (by quoting the value) caused other problems. Will need to wait for the backend to properly fix the root problem. More... over 21 years ago
Fix in updateable result sets to handle binding null values correctly Patch submitted by Kris Jurka (applied with some modifications) More... over 21 years ago
Fixed support in jdbc for 7.3 server autocommit. With these changes the jdbc regression tests pass for both autocommit on and autocommit off More... over 21 years ago
fixed missing apostrophe More... over 21 years ago
test files added by Kris Jurka More... over 21 years ago
Fixed test suite to call PoolingDataSourceTest which was missed More... over 21 years ago
schema awareness patch provided by Kris Jurka More... over 21 years ago
Applied patch from Aaron Mulder ([email protected]) that fixes jdbc datasource support for jdk1.4/jdbc3 More... over 21 years ago
Added regression test for using server side prepared statements in jdbc and fixed a bug found by the regression test More... almost 22 years ago
Patches submitted by Kris Jurka ([email protected]) for the following bugs: - Properly drop tables in jdbc regression tests with cascade for 7.3 - problem with Statement.execute() and executeUpdate() not clearing binds - problem with ResultSet not correctly handling default encoding - changes to correctly support show transaction isolation level in 7.3 - changed DatabaseMetaDataTest to handle differences in FK names in 7.3 - better fix for dynamically checking server NAME data length (With the fixes above the jdbc regression tests pass on jdbc2 and jdbc3 against both a 7.2 and 7.3 server) Patchs submitted by David Wall ([email protected]): - problem with getBlob when largeobject oid is null - improvements to BlobOutputStream Patch submitted by Haris Peco ([email protected]): - problem with callable statement not supporting prepared statement methods More... almost 22 years ago
Fixed DatabaseMetaData to correctly handle NAME size of 64 Fixed Statement to correctly DEALLOCATE any prepared statements More... almost 22 years ago
Run pgjindent for Java folks.
tester_123
as Bruce Momjian
More... almost 22 years ago
Remove all traces of multibyte and locale options. Clean up comments referring to "multibyte" where it really means character encoding. More... almost 22 years ago
JDBC checkin fixing the following bugs: Fixed support in the driver for notifications (added PGConnection.getNotifications()) - problem reported by [email protected] Worked around server problems with int8/int2 and constants; quote values when they are intended to bind to an int8/int2 column - reported by many Fixed bug in the Array interface with string parsing not handling escaped characters correctly - reported by [email protected] Added workaround to support 'infinity' and '-infinity' for dates - reported [email protected] Fixed some performance issues with setBlob - reported by [email protected] Added support for using new prepared statements functionality in 7.3 (added PGStatement.setUseServerPrepare() and isUseServerPrepare() methods) More... almost 22 years ago
patch from Thomas O'Dowd to ensure that connections are closed More... almost 22 years ago
testing for insertRow More... almost 22 years ago
patch to allow insertRow on an empty resultSet More... almost 22 years ago
Changed to reflect the current reality, ie we do support updateable resultsets More... almost 22 years ago
Enhancements to how queries with bind values are stored internally and sent to the server. Previously we allocated a new String object for the entire final query we were sending to the database. If you had a big query, or especially if you had large bind values you ended up with essentially two copies in memory. This change will reuse the existing objects and therefore should take 1/2 the memory it does today for a given query. This restructuring will also allow in the future the ability to stream bytea data to the server instead of the current approach of pulling it all into memory. I also fixed a test that was failing on a 7.2 database. Also renamed some internal variables and some minor cleanup. More... almost 22 years ago
Removed code that is no longer used and has been commented out for the last two releases. More... almost 22 years ago