"Morten Gulbrandsen" <[EMAIL PROTECTED]> wrote: > > I use Version DBMS MySQL 3.23.55 runing under Windows 2000. > > I have coded this from a textbook; > === > > > C:\mysql\bin>type constraint.sql > USE company; > > DROP TABLE IF EXISTS EMPLOYEE; > > CREATE TABLE EMPLOYEE > ( > FNAME VARCHAR(15) NOT NULL, > MINIT CHAR, > LNAME VARCHAR(15) NOT NULL, > SSN CHAR(9) NOT NULL, > BDATE DATE, > ADDRESS VARCHAR(30), > SEX CHAR, > SALARY DECIMAL(10,2), > SUPERSSN CHAR(9), > DNO INT NOT NULL DEFAULT 1, > > CONSTRAINT EMPPK > PRIMARY KEY (SSN), > > CONSTRAINT EMPSUPERFK > FOREIGN KEY (SUPERSSN) REFERENCES EMPLOYEE(SSN) > ON DELETE SET NULL ON UPDATE CASCADE, > > CONSTRAINT EMPDEPTFK > FOREIGN KEY (DNO) REFERENCES DEPARTMENT(DNUMBER) > ON DELETE SET DEFAULT ON UPDATE CASCADE) TYPE = InnoDB; > > DESCRIBE EMPLOYEE; > > C:\mysql\bin> > > === > > > This is what happens : > > > === > > C:\mysql\bin>mysql -vvv < constraint.sql > -------------- > DROP TABLE IF EXISTS EMPLOYEE > -------------- > > Query OK, 0 rows affected (0.00 sec) > > -------------- > CREATE TABLE EMPLOYEE > ( > FNAME VARCHAR(15) NOT NULL, > MINIT CHAR, > LNAME VARCHAR(15) NOT NULL, > SSN CHAR(9) NOT NULL, > BDATE DATE, > ADDRESS VARCHAR(30), > SEX CHAR, > SALARY DECIMAL(10,2), > SUPERSSN CHAR(9), > DNO INT NOT NULL DEFAULT 1, > CONSTRAINT EMPPK > PRIMARY KEY (SSN), > > CONSTRAINT EMPSUPERFK > FOREIGN KEY (SUPERSSN) REFERENCES EMPLOYEE(SSN) > ON DELETE SET NULL ON UPDATE CASCADE, > CONSTRAINT EMPDEPTFK > FOREIGN KEY (DNO) REFERENCES DEPARTMENT(DNUMBER) > ON DELETE SET DEFAULT ON UPDATE CASCADE) TYPE = InnoDB > -------------- > > Query OK, 0 rows affected (0.00 sec) > > -------------- > DESCRIBE EMPLOYEE > -------------- > > +----------+---------------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +----------+---------------+------+-----+---------+-------+ > | FNAME | varchar(15) | | | | | > | MINIT | char(1) | YES | | NULL | | > | LNAME | varchar(15) | | | | | > | SSN | varchar(9) | | PRI | | | > | BDATE | date | YES | | NULL | | > | ADDRESS | varchar(30) | YES | | NULL | | > | SEX | char(1) | YES | | NULL | | > | SALARY | decimal(10,2) | YES | | NULL | | > | SUPERSSN | varchar(9) | YES | | NULL | | > | DNO | int(11) | | | 1 | | > +----------+---------------+------+-----+---------+-------+ > 10 rows in set (0.00 sec) > > Bye > > C:\mysql\bin> > > === > > My problem is, I want some feedback from MySQL that my versions actually > supports those statements, including innodB and all additional > constraint information, Describe does not give me feedback about > foreign keys and referential triggered actions. > > Is InnoDB the correct table type for properly supporting referential > triggered actions, please ? > > If not, what can I do instead ? Upgrade to some newer > MySQL version please ?
You can see foreign key definitions using SHOW CREATE TABLE or SHOW TABLE STATUS statements. ON UPDATE CASCADE works since 4.0.8. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
