Here is the table I made:
mysql> show create table notes; +-------+----------------------------------------------------+ | Table | Create Table | +-------+----------------------------------------------------+ | notes | CREATE TABLE `notes` ( `id` int(11) NOT NULL auto_increment, `note` text NOT NULL, `status` enum('active','hidden','deleted','followup','starred') default NULL, `created` datetime NOT NULL, `last_updated` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 | +-------+----------------------------------------+
I am trying to add a foreign key constraint:
mysql> alter table notes add constraint foreign key(`id`) references `notetypes`.`id` on update cascade on delete restrict; Query OK, 0 rows affected (0.15 sec) Records: 0 Duplicates: 0 Warnings: 0
No mistakes! No warnings! For this reason, I have been using an internal database for some time without foreign keys (provided that they are present). Any idea if this is a mistake, or am I doing something wrong? Any workarounds or options in mysql that would avoid such errors?
$ mysql --version mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2
thanks
In JP
JP19
source share