You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2002/05/08 18:45:59 UTC
PLEASE UPDATE /james/lib/mysql jar file!
> More overly, I'm pretty sure the problem is with the JDBC driver... I'd
> bet it's mysql, and while I'm not really expert about that db, there
> seems to be a meg limit on the binary field by default.
PLEASE FIX THIS: James is including an ANCIENT version of the mm.mysql
driver. The current release is v2.0.13; James is shipping version 2.0.4
(25JAN01). Amongst the missing fixes:
06-13-01 - Fixed ResultSet.getBlob() ArrayIndex out-of-bounds
- Fixed ResultSetMetaData.getColumnTypeName for TEXT/BLOB
- Fixed ArrayIndexOutOfBounds when sending large BLOB queries
(Max size packet was not being set)
The hard limit on the store is effectively set by the client server
protocol. According to the MySQL 3.X manual, "the server/client protocol
and MyISAM tables has currently a limit of
16M per communication packet / table row," so that would be our limit.
The driver is available from http://mmmysql.sourceforge.net/.
--- Noel
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: PLEASE UPDATE /james/lib/mysql jar file!
Posted by Danny Angus <da...@thought.co.uk>.
> and I suspect that Mark would be willing
> to provide
> it under the Apache license, too.
I gather not.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: PLEASE UPDATE /james/lib/mysql jar file!
Posted by "Noel J. Bergman" <no...@devtech.com>.
What? Why is that? The driver is LGPL, so it doesn't have the viral
consequences of the GPL, and I suspect that Mark would be willing to provide
it under the Apache license, too.
--- Noel
-----Original Message-----
From: Danny Angus [mailto:danny@thought.co.uk]
Sent: Thursday, May 09, 2002 9:12
To: James Developers List
Subject: RE: PLEASE UPDATE /james/lib/mysql jar file!
Actually we may have to pull the driver from the distro altogether for legal
reasons.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: PLEASE UPDATE /james/lib/mysql jar file!
Posted by Danny Angus <da...@thought.co.uk>.
Actually we may have to pull the driver from the distro altogether for legal
reasons.
-----Original Message-----
From: Noel J. Bergman [mailto:noel@devtech.com]
Sent: 08 May 2002 17:46
To: James Developers List
Subject: PLEASE UPDATE /james/lib/mysql jar file!
> More overly, I'm pretty sure the problem is with the JDBC driver... I'd
> bet it's mysql, and while I'm not really expert about that db, there
> seems to be a meg limit on the binary field by default.
PLEASE FIX THIS: James is including an ANCIENT version of the mm.mysql
driver. The current release is v2.0.13; James is shipping version 2.0.4
(25JAN01). Amongst the missing fixes:
06-13-01 - Fixed ResultSet.getBlob() ArrayIndex out-of-bounds
- Fixed ResultSetMetaData.getColumnTypeName for TEXT/BLOB
- Fixed ArrayIndexOutOfBounds when sending large BLOB queries
(Max size packet was not being set)
The hard limit on the store is effectively set by the client server
protocol. According to the MySQL 3.X manual, "the server/client protocol
and MyISAM tables has currently a limit of
16M per communication packet / table row," so that would be our limit.
The driver is available from http://mmmysql.sourceforge.net/.
--- Noel
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>