Emmanuel Lecharny wrote:
David Boreham wrote:
I would recommend not trying to use the auto-increment primary key
approach with a DS.
It won't work.
Instead change the data model to use a UUID in place of the monotonic
increasing integer.
That's an option, except when your client need to manipulate an int or
a long, as an UUID will be 128 bits long :/
You can try tricks like truncating the UUID to 32-bits but it's best to
re-design the client to not have this restriction.
At some point you have go also consider giving up and answering the
statement 'but I can do xyz with a
relational database' with 'well, then use a relational database'. Except
the RDBMS would have exactly the
same problem with the integer ID when you try to deploy replication or
partitioning...
