My webapp continues to grow and I would appreciate any comments monks might have on the use of INNODB tables in MySQL.
The major reason I am considering them to provide what is essentially a 'super ENUM' operation. I want to be able to define a series of say 'user-types' which I can change and using the 'ON DELETE CASCADE' action I can delete all users who have the user-type which is being deleted. Alternatively I can use the 'ON DELETE SET NULL' and then remove the users with the appropriate set to NULL as a scheduled admin task in the quiet time.
I can see one problem: It does not seem that Class::DBI could be used for manipulations where a foreign key is involved as it will atempt to bypass the referential integrity features of the InnoDB tanble type.
Any and ALL comments (bricks, rotten tomatoes and mouldy socks included) would be welcome!
In reply to Class::DBI with MySQL INNODB tables by jdtoronto
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |