On Saturday, May 31, 2014 11:10:00 AM CEST, Axel Rau wrote:
I’m usually using primary key sequences with increment > 1 for that (1,3,5,7 on primary server, 2,4,6,8 on secondary).
If you have a natural primary key, you can either declare that using SQL syntax, or not. There is no middle way.
If you declare it, then you're stuck with how that key behaves. If it won't increase in pairs, then so be it.
If you don't declare it, and use a primary key sequence instead, then you have the mongodb problem. Basically the same as not declaring "unique" in a column that's unique in the requirements specification. Sure, you can do it and it makes the RDBMS stop complaining. I hope you're not suggesting that?
Arnt
