Re: MDB2 MySQL(i) constraints issues
| From: | Lukas Kahwe Smith | Date: | Sat, 14 Oct 2006 13:13:45 +0000 |
| Subject: | Re: MDB2 MySQL(i) constraints issues | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44521@lists.php.net to get a copy of this message | ||
Rob Siveter wrote:
Hi I have come across a problem whilst extending both listTableConstraints() and getTableConstraintDefinition() (in MDB2/Driver/Reverse/ and MDB2/Driver/Manager/ for MySQLi.php) to support Foreign Keys with MySQL. As MySQL handles unique indexes completely separate from FK constraints, both constructs may have an instance of the same name! This means that listTableConstraints (which assumes uniqueness) currently will only bring back one occurance of the name, but bringing back two without reference to the 'type' would make no sense. However apparently the API for these functions is locked down. getTableConstraintDefinition() is worse as it simply will not know which constraint the definition is being requested for. Both functions probably require additional optional parameters and/or extended return variables.just wanted to bring you two together on this: http://oss.backendmedia.com/MDB2/ToDo regards, Lukas