On Fri, 25 Mar 2005 15:42:50 -0600 Russell E Glaue <[EMAIL PROTECTED]> 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.
Thanks for your patience, and I'm glad you got it working against 4.0. I would encourage you to try actually running the SQL statement in MySQL 4.1 separately. Here is the sqlResources.xml in SVN:
http://svn.apache.org/viewcvs.cgi/james/server/branches/branch_2_1_fcs/src/conf/sqlResources.xml?rev=109137&view=markup
You'll see the create logic is:
CREATE TABLE ${table} (
message_name varchar (200) NOT NULL,
repository_name varchar (255) NOT NULL,
message_state varchar (30) NOT NULL ,
error_message varchar (200) NULL ,
sender varchar (255) NULL ,
recipients text NOT NULL ,
remote_host varchar (255) NOT NULL ,
remote_addr varchar (20) NOT NULL ,
message_body longblob NOT NULL ,
message_attributes longblob NULL ,
last_updated datetime NOT NULL,
PRIMARY KEY (repository_name, message_name)where $(table) is based on your db://<databasepool>/<table>/ string. I was thinking maybe it was some weird double-byte issue, but looking at the create script, 200+255 = 455, so even if we had mistakenly used double-bytes, that's 455 x 2 < 1000.
I'll try to test MySQL 4.1 with that statement at some point. I'm still using 4.0 though primarily.
-- Serge Knystautas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
