Error on Startup: key PRIMARY in userEvents

Reply to Error on Startup: key PRIMARY in userEvents on Thu, 06 May 2010 15:00:23 GMT

apl — Thu, 06 May 2010 15:00:23 GMT

running the script line by line in MYSQL Query Browser fixes the database.

If you want me to test this with the next release post me a rc of that.

So I consider this bug as closed.

Arne

Reply to Error on Startup: key PRIMARY in userEvents on Thu, 06 May 2010 13:36:06 GMT

mlohbihler — Thu, 06 May 2010 13:36:06 GMT

Yes, there should have been a type=InnoDB in there. I've added this script to the db upgrade for the next version:


alter table userEvents engine=InnoDB;
delete from userEvents where eventId not in (select id from events);
delete from userEvents where userId not in (select id from users);
alter table userEvents add constraint userEventsFk1 foreign key (eventId) references events(id) on delete cascade;
alter table userEvents add constraint userEventsFk2 foreign key (userId) references users(id) on delete cascade;

Reply to Error on Startup: key PRIMARY in userEvents on Thu, 06 May 2010 08:55:20 GMT

apl — Thu, 06 May 2010 08:55:20 GMT

It looks that MYISAM does not suppport foreign keys orums.mysql.com/read.php?21,213549,213549

so maybe run a script on 1.8.3 if mysql db is used.
Switch that table to innodb and try to create the foreign keys that are missing (at least in my db, which I have restored from backups).

Arne

Reply to Error on Startup: key PRIMARY in userEvents on Thu, 06 May 2010 08:40:07 GMT

apl — Thu, 06 May 2010 08:40:07 GMT

It 5.1.41 and the version in ubuntu 09.10

maybe its that the table userEvents is a myISAM Table.
The statement type=InnoDB on the table in line 274 createTables-mysql.sql is missing - bug/typo?.

Arne

Reply to Error on Startup: key PRIMARY in userEvents on Tue, 04 May 2010 14:12:41 GMT

mlohbihler — Tue, 04 May 2010 14:12:41 GMT

There should be a foreign key between events and eventUsers, so having event ids values in the latter not in the former should not have been possible. What version of MySQL are you using? I believe older versions didn't enforce constraints completely.

Reply to Error on Startup: key PRIMARY in userEvents on Tue, 04 May 2010 08:45:48 GMT

apl — Tue, 04 May 2010 08:45:48 GMT

Yes,

This is mysql the numbers in userEvent ar much higher than the numbers in evnets so it will insert numbers in userEvents, which already.

After deleting all values in userEvents and Events its running. Ive got a backup ;-)

Arne

Reply to Error on Startup: key PRIMARY in userEvents on Sun, 02 May 2010 23:18:45 GMT

mlohbihler — Sun, 02 May 2010 23:18:45 GMT

The keys that were being inserted (726-3, representing eventId and userId) are very small - very unlikely there is any kind of overflow going on. Is this MySQL?