Right, but when you write your script (or whatever) that cleans these
keys up and does the merge, you're where you started -- arbitrary
integer keys with no meaning. If you merge databases where the keys are
*supposed* to have meaning, you then have to mangle *real* data to make
them merge.
Ron Johnson wrote:
OK, let's use a synthetic key on the sales master table. In fact,
*both* companies have a synthetic key on their sales master tables.
OMG, conflicting/overlapping synthetic keys!!!!!
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/