In a transition from an old system to a new one most of the client records
were carried over, however, some escaped. Now I have some system-assigned
ID numbers that should be a previously existing number.
After rereading Bill Downall's page on cascading updates and deletes I agree
this is not a feature I'd want on full-time, but can I ALTER TABLE to add
cascade, perform the updates, then ALTER TABLE again to drop cascade?
(I know I can, I guess the question is whether I should).
If this would work what are the other considerations? For instance, I'd
only perform this with MULTI OFF.
If the greater issue is changing a client ID number what other strategies
are there? Given the PK/FK relationships based on this number we _could_
create a 2nd client record with the correct ID, then reassign the FK tables,
but that's pretty labor intensive and relies upon a record duplication which
is another layer of management detail to correct.
tia
Dave Ebert
[EMAIL PROTECTED]
