[mothered]

Yea but in case when you have for example 10 nested relations you have to "manually" one by one remove the FKeys

Agree.

As mentioned, It Is messing around a bit, but you can have your SQL ready and only change the table names and Foreign keys accordingly.
For example:

* Delete the Foreign key from the `User Data` table (child table):

Code:

ALTER TABLE `User Data` DROP FOREIGN KEY `User Data_ibfk_1`;

* Do whatever you wish to the parent table (which Is `User IDs`), and then add the Foreign key back Into child table (which Is `User Data`).  I've used the ON UPDATE & ON DELETE CASCADE clauses for demonstration purposes:

Code:

ALTER TABLE `User Data` ADD FOREIGN KEY (mothered) REFERENCES `User IDs` (mothered) ON UPDATE CASCADE ON DELETE CASCADE;

It's not too time consuming to only alter the table names & respective Foreign keys.

I totally agree

Are you proficient In SQL?

[darkninja1980]

Agree.

As mentioned, It Is messing around a bit, but you can have your SQL ready and only change the table names and Foreign keys accordingly.
For example:

* Delete the Foreign key from the `User Data` table (child table):

Code:

ALTER TABLE `User Data` DROP FOREIGN KEY `User Data_ibfk_1`;

* Do whatever you wish to the parent table (which Is `User IDs`), and then add the Foreign key back Into child table (which Is `User Data`).  I've used the ON UPDATE & ON DELETE CASCADE clauses for demonstration purposes:

Code:

ALTER TABLE `User Data` ADD FOREIGN KEY (mothered) REFERENCES `User IDs` (mothered) ON UPDATE CASCADE ON DELETE CASCADE;

It's not too time consuming to only alter the table names & respective Foreign keys.

I totally agree

Are you proficient In SQL?

yes I am

[mothered]

I totally agree

Are you proficient In SQL?

yes I am

Good to read.

When appropriate, we can converse about It.

[darkninja1980]

Are you proficient In SQL?

yes I am

Good to read.

When appropriate, we can converse about It.

sure