> So how is it possible to drop a foreign key in a master / slave
replication
> ? the autogenerated-naming constraint should be different ?
I have no idea.
> How automatic database structure update can be executed (from a script
> generetor like PowerDesigner) ?
With regards,
Martijn Tonies
So how is it possible to drop a foreign key in a master / slave replication
? the autogenerated-naming constraint should be different ?
How automatic database structure update can be executed (from a script
generetor like PowerDesigner) ?
thanks...
""Martijn Tonies"" <[EMAIL PROTECTED]> a écrit
Hello,
> I have problem in naming foreign key constraints :
--8<--
> Actually, the name for the just created constraint is an 'internally
> generated id' (i.e :0_023), so the update script can't find the named
> constraint 'fktblnumb'
>
> The "show create table tblnumbers" outputs :
>
> CREATE
Hi,
I have problem in naming foreign key constraints :
Engine : mySql 4.1.1 and/or 5.0.0a
System : Windows 2000 sp4 and / or win NT 4 sp6a
Here is a script example of what I need to do :
/* Script 1 */
CREATE TABLE tblphone (
nameid INT PRIMARY KEY AUTO_INCREMENT,
fnameVARCHAR(30),
