I'm using MySQL 5.0.1-alpha, using db:// configuration, and I don't have
any problems.
Vincenzo
Russell E Glaue wrote:
Ya, well I tried all this. Except for actually running the SQL
statement in MySQL separately. I could not discover what SQL state was
giving the problem.
I turned DEBUG on for logging, but it is not verbose enough about the
communication to MySQL. That should be changed so to record what JAMES
is actually saying to MySQL. Right now JAMES is only records what
MySQL is saying to it.
Well what I did do was look over every "CREATE TABLE" sql statement to
make sure they were all correct. And they all are. They are all fine.
What I ended up doing was downgrading to MySQL 4.0.27. When I
downgraded to this version, using the JDBC driver mysql-jdbc-3.1.7,
JAMES will initialize the MySQL database without error. And it runs fine.
So this tells me that JAMES is not fully compatible with MySQL 4.1.x.
I know everyone may want to disagree.
Now I know JAMES partially works with MySQL 4.1 because I read another
posting where someone was using it for dbfile:// configuration.
Since I am using this for a db:// configuration, and the mailstore is
the one being complained about, I would assume that JAMES is not
compatible with MySQL 4.1 100%, mainly with mailstore initialization.
So, Is this is a bug that will need to be addressed?
Would one of the developers like to quickly try JAMES with mysql
4.1.10 and report back on their experience? Make sure you configure
JAMES to use MySQL for all storage, using db:// configuration.
-RG
Serge Knystautas wrote:
On Fri, 25 Mar 2005 12:01:47 -0600
Russell E Glaue <[EMAIL PROTECTED]> wrote:
java.sql.SQLException: Specified key was too long; max key length is
1000 bytes
Hmm, that is weird. I'm only using MySQL 4.0, but I can't imagine
this being a problem with the point release. What I might suggest is
opening sqlResources.xml, finding the SQL statement that gets run
(hopefully file is obvious enough), and running it in a MySQL tool.
Hopefully you'll get a bit more information about why that is
failing. You might also check the mysql docs on the off-chance they
have more information about that error message.
--
Serge Knystautas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
