Noel J. Bergman wrote:
Stefano Bagnara wrote:
Noel J. Bergman wrote:
Stefano Bagnara wrote:
Where did you read that mysql recommend to downgrade to 2.0.14
as a workaround for memory leaks?
See http://bugs.mysql.com/bug.php?id=20003, particularly the second
paragraph of the author's response.
Ok, I see, but this is not mysql AB recommending to downgrade, but the
user reporting this issue that say that *his* issue does not appear with
mm-mysql.
No ... read the second paragraph of THE AUTHOR'S response. Mark Matthews,
THE AUTHOR of the driver and an employee of MySQL AB, wrote:
Earlier versions of the driver didn't maintain references
to these open statements and result sets (as is required
by the JDBC spec), so they would be eligible for GC as
soon as your application was done with them.
So that "leak" wouldn't occur with the v2 driver.
I agree that that very leak was not present in mm-mysql but Mark
Matthews is not reccomending to downgrade to 2.0.14.
mm-mysql 2.0.14 is old and no more supported. It does not correctly
support newer mysql version (and by newer I mean ALL the versions
currenlty supported by mysql AB: 4.x and 5.x) and I had much more
problem when using it than now that I use a beta of 5.0.0 (I didn't
update to 5.0.3 yet). Thinking that nowadays mysql ab suggested to
downgrade to 2.0.14 was making me sick, so I searched the thread and I'm
happy they never told something similar ;-)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
