Subject | Re: [firebird-support] Re: parameter mismatch for procedure |
---|---|
Author | Nando Dessena |
Post date | 2007-01-19T13:24:09Z |
Ron,
rs> My intention was to merge databases some time in the
rs> future, where all members of one Broker will remain attached to that
rs> broker and no other broker. I woould like the PK to be an integer
rs> rather than a GUID, which will guarantee uniqueness.
While I personally think that a GUID (or other flavours of
statistically unique value generation) is a decent enough and
hassle-free solution for distributed ID generation, there are other
mechanism. You could do something as simple as assigning each
site/database an unique ID and make it part of the key (or use it
while merging databases). Search the net for information about the
high-low strategy, and/or look here:
http://www.ddj.com/184415770
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================
rs> My intention was to merge databases some time in the
rs> future, where all members of one Broker will remain attached to that
rs> broker and no other broker. I woould like the PK to be an integer
rs> rather than a GUID, which will guarantee uniqueness.
While I personally think that a GUID (or other flavours of
statistically unique value generation) is a decent enough and
hassle-free solution for distributed ID generation, there are other
mechanism. You could do something as simple as assigning each
site/database an unique ID and make it part of the key (or use it
while merging databases). Search the net for information about the
high-low strategy, and/or look here:
http://www.ddj.com/184415770
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================