[[email protected]]

I have deleted the database and have reimported it to start again now that this bug has been fixed

Regards

Richard

[[email protected]]

thanks for your quick replies – I'll download the new version

Regards

Richard

[[email protected]]

I have now checked and found the foreign key is created – however it is not shown when using the manage relationships form as advised in documentation- details below. Is this a bug?

Regards

Richard

Column Information For – transact_mysql.unspsc

---

Field Type Collation Null Key Default Extra Privileges Comment

---

---

---

---

---

---

---

---

---

code int(10) NULL PRI 0 select,insert,update,references

name varchar(255) latin1_swedish_ci YES (NULL) select,insert,update,references

version int(10) NULL YES MUL (NULL) select,insert,update,references

Index Information For – transact_mysql.unspsc

---

Table Non_unique Key_name Seq_in_index Column_name Collation Cardinality Sub_part Packed Null Index_type Comment

---

---

---

---

---

---

---

---

---

---

---

---

unspsc 0 PRIMARY 1 code A 14239 (NULL) (NULL) BTREE

unspsc 1 version 1 version A 5 (NULL) (NULL) YES BTREE

DDL Information For – transact_mysql.unspsc

---

Table Create Table

---

---

unspsc CREATE TABLE `unspsc` (

`code` int(10) NOT NULL default '0',

`name` varchar(255) default NULL,

`version` int(10) default NULL,

PRIMARY KEY (`code`),

KEY `version` (`version`),

CONSTRAINT `unspsc_ibfk_1` FOREIGN KEY (`version`) REFERENCES `unspsc_version` (`ver_id`) ON DELETE CASCADE ON UPDATE CASCADE,

) ENGINE=InnoDB DEFAULT CHARSET=latin1

[Author]

Posts