Make sure your my.cnf has innodb enabled. The issue is probably because skip innodb is turned on.
Regards J Duggan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Sterenborg Sent: 10 December 2008 10:53 To: [email protected] Subject: [policyd-users] Cluebringer MySQL tables Hi, I'm trying to setup cluebringer-2.0.5 with MySQL-5.1.30. When creating the tables I'm having a problem with this part (from generated policyd.mysql file, comments omited): CREATE TABLE greylisting_tracking ( TrackKey VARCHAR(512) NOT NULL, Sender VARCHAR(255) NOT NULL, Recipient VARCHAR(255) NOT NULL, FirstSeen BIGINT UNSIGNED NOT NULL, LastUpdate BIGINT UNSIGNED NOT NULL, Tries BIGINT UNSIGNED NOT NULL, Count BIGINT UNSIGNED NOT NULL, UNIQUE(TrackKey,Sender,Recipient) ) TYPE=InnoDB CHARACTER SET latin1 COLLATE latin1_bin; I'm getting an error: "SQL Error: Specified key was too long; max key length is 1000 bytes" The database has this charset/collation: default-character-set=latin1 default-collation=latin1_general_ci Searching around I found I have to lower the size of some VARCHAR fields to make it work (512+(2*255)=1022). When I did that I got no error but when searching the archives, I found a reference to this when using UTF8 pointing out that domain names can be 255 chars, so I guess reducing the field size to 244 (512+(2*244)=1000) is not the solution. Since I suppose there is a reason that TrackKey is 512 bytes, I don't know how I can fix this. Grts, Rob _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
