On Thursday, January 12, 2012 9:02:35 am David Johnston wrote:
> ----------------------------------------
>
> Adrian, you are not helping...if ON UPDATE CASCADE was enabled on "orders"
> the error in question would never have appeared and the UPDATE would have
> succeeded. Carlos' goal is to change the value of a Primary Key that has
> already been used in a FOREIGN KEY constraint and he needs to learn to use
> the documentation to solve some of these basic questions instead of asking
> the list. His approach is correct, execute UPDATE against the
> "developers" table.
My mistake, I got the table relationship order wrong. Sorry for the noise.
>
> David J.
--
Adrian Klaver
adrian.klaver@gmail.com