|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
Stay one step ahead of the competition. Evaluate and give feedback
on some of the hottest web development tools on the market today.
Make your opinion heard! Click
Here
|
|
#1
|
|||
|
|||
|
innodb reverting to myisam?
I've been trying to create innodb tables to support foreign key constrains. But when I test them, they're not working(Ii insert a non-existant parent value into the child FK and it's accepted). And when I 'show create table' they come up as 'myisam'.
I even tried using the simple examples in the mysql.com documentation ( documentation ): CREATE TABLE parent(id INT NOT NULL, PRIMARY KEY (id)) TYPE=INNODB; CREATE TABLE child(id INT, parent_id INT, INDEX par_ind (parent_id), FOREIGN KEY (parent_id) REFERENCES parent(id) ON DELETE SET NULL ) TYPE=INNODB; and 'show create table' gives me: | child | CREATE TABLE `child` ( `id` int(11) default NULL, `parent_id` int(11) default NULL, KEY `par_ind` (`parent_id`) ) TYPE=MyISAM | and | parent | CREATE TABLE `parent` ( `id` int(11) NOT NULL default '0', PRIMARY KEY (`id`) ) TYPE=MyISAM | My host is running 3.23.53 |
|
#2
|
|||
|
|||
|
and 'show create table' gives me:
what software are you using? sounds like it's just bad software =o if you're not getting syntax errors on the REFERENCES keyword, then the table types are obviously InnoDB |
![]() |
| Viewing: Dev Articles Community Forums > Databases > General SQL Development > innodb reverting to myisam? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|