InnoDB tables. Foreign key support is a must have. I've been using
MySQL 4.0.x with InnoDB tables for James 2.2.0 in the past with no issues.
BTW, if I switch to MyISAM, I get the same problem only the max key
length is 1000 bytes instead of 1024.
message_name is only 200 by default currently. Are you suggesting that
it should be increased further?
Thanks,
Eric
Stefano Bagnara wrote:
James 2.2.0
MySQL 4.1.13
Connector/J 3.1.8a
InnoDB or MyISAM tables?
I'm almost sure I've tested MySQL 4.1.13 with MyISAM and it worked like a
charm.
If I change the statement above so that the messagename
varchar length +
the repository_name varchar length = 341 (1024/3) or lower, then the
statement works.
Don't reallly know why it need 3 bytes indexes per each char.
Any thoughts on the problem and how to solve it?
Could I hack the sqlResources.xml and change the lengths so that they
equal 341 only? Does repository_name have to be 255? If that is a
valid option, what is the suggested ratio (200/191, 150/191, etc)?
I would go for 255 message_name and remaining chars for repository_name.
Stefano
---------------------------------------------------------------------
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]
