[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-java
Subject:    Re: Default ResultSet holdability inconsistency problem
From:       Mark Matthews <mark () mysql ! com>
Date:       2006-03-10 14:32:57
Message-ID: 44118E19.6080509 () mysql ! com
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

G Winstanley wrote:
> I am in the process of debugging my connection pooling library and I
> seem to have uncovered an inconsistency in the ResultSet holdability of
> MySQL. Perhaps I am missing the point, but my presumption is that the
> holdability for a Statement should be the same as the default for the
> Connection that created it, assuming a non-default holdability was not
> specified.
> 
> From my tests, and looking at the driver source, it seems that the
> default Connection holdability is CLOSE_CURSORS_AT_COMMIT, but the
> holdability in a created statement is HOLD_CURSORS_OVER_COMMIT. Can
> anyone explain why this is the case?
> 
> For reference:
> 	MySQL 5.0.18-nt
> 	MySQL Connector/J 3.1.12
> 
> Stan
> 

Stan,

There's really no cursors held (since MySQL doesn't have them). I can
make the two classes consistent, but you're not affecting locks or
anything on the server side.

	-mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEEY4ZtvXNTca6JD8RAi+0AJwJtacvdskQEcN+piuoFZlgEbT+7ACeL5Sq
fYezqCv4XIr3zSImHUiU3mk=
=lLAL
-----END PGP SIGNATURE-----

-- 
MySQL Java Mailing List
For list archives: http://lists.mysql.com/java
To unsubscribe:    http://lists.mysql.com/java?unsub=mysql-java@progressive-comp.com

[prev in list] [next in list] [prev in thread] [next in thread]