MDB2 MySQL(i) constraints issues
| From: | Rob Siveter | Date: | Tue, 10 Oct 2006 16:26:25 +0000 |
| Subject: | MDB2 MySQL(i) constraints issues | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-44453@lists.php.net to get a copy of this message | ||
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.
Can anyone advise?
thanks
Rob Siveter
--
Premier IT
New Premier House
150 Southampton Row
London
WC1B 5AL
t: 020 7837 2690
f: 020 7278 3113