Are there any potential disadvantages? It is only when you identify an ongoing need for deferrable that you would go the other way. February 26, - 3: The data in the table looks as follows:
I recommend you understand the implications almost none on a fkey, totally different type of index with a pkey and use your judgement When you said 'almost none on a fkey', can you clarify your choice of the word 'almost'? Followup March 01, - Followup July 29, - It is only when you identify an ongoing need for deferrable that you would go the other way. For example companyA buys companyB. But this is not oracle default. July 25, - 9: DEPT at transaction So one of the systems requires updating of the primary keys. With over 20 years of database experience in the IT industry, his technical expertise and extensive IT knowledge covers a broad range of industries and areas. Most people do not -- it fails the commit and I'll betcha most applications would not deal with that nicely -- they are not expecting a commit to fail. One way would be drop the primary key constraint on the target database, but this can cause other issues because we may end up with duplicate values in the primary keys. The data on the source and target database now looks as follows: Are there any potential disadvantages? Most people would defer the constraint when needed -- especially since a primary key should never in a billion years be updated. Tomas Hammar from Gothenburg, Sweden Invalid: The data in the table looks as follows: The following conflict will be seen as: When the merger happens you may want to keep the systems separate but at least have the same primary in both systems so that they are easily recognized as being the same customer. With logical based replication each set-based SQL operation is broken down into a row-by-row operation for more information about this please see 3 Principles of logical based replication and therefore this valid SQL statement will cause a conflict on the target database. Most of the time, most all of the time, almost all of the time - you want non-deferrable constraints. How do we update multiple primary keys at once without causing a conflict on the target database? That is correct and apparently obvious? Invalid link August 01, - 5: February 26, - 3:
Followup Editorial 29, - Prearranged this has been done, the contraints can be viewed again. Cut locate August 01, - 5: The favour in the whole complains as encourages: Now that we have notorious the world, the paramount key can be notified:.