[Jez]

Hi, Neshi

Glad you've got those keys sorted.

As you've discovered, you don't actually need version 4 of MySQL to use InnoDB and pk/fk relationships. They've been available in the source code version of MySQL since 3.23.34a. If you're using a recent version (e.g. 3.23.55 or 3.23.56) you also shouldn't have to use the Max Windows binary – I've found the mysqld and mysqld-nt version both support InnoDB and pk/fk relationships.

Having said that version 4 is a bit easier to set up, although if you're working exclusively with InnoDB you will need to add the default-table-type=innodb option in the my.ini file to set InnoDB as the default table type.

Jez

[Jez]

Hi, Neshi

Connect to your MySQL database with SQLyog and use the SQLyog Object Browser to locate a pair tables which you are trying to relate with primary and foreign keys.

Double-click the first table and then single-click in the Objects pane at the bottom of the SQLyog window. Press Ctrl + A to select all the text in the pan and then Ctrl + V to paste this into your a post to this forum.

Repeat this process with the second table and send us your posting.

We can then determine whether it's the SQL statements which are at fault. If not, it may be a configuration issue with MySQL, but let's cross that bridge if and when we get to it…

Jez

[Jez]

Hi, Cal

Thanks for the reply.

I think my vote's also going for a Windows glitch rather than SQLyog as I have been unable to replicate the behaviour on a Win98 machine this morning.

They call me Dr Format in the office as I always go for separate Windows and data partitions and do a clean reinstall when Windows ****s up. Nevertheless, your 'overload' suggestion might be more suitable for my student.

I think Linux is probably not what the doctor ordersed for him, but I'm seriously considering myself so thanks for the web link.

Cheers

Jez

[Author]

Posts