Neil Tiffin wrote:
> I have not even considered multiple database servers running different
> database, which is our design goal. In this case we would like to have
> a slimmed down (and blazingly fast) PostgreSQL server in which we manage
> the uid in our middleware. This is because the uid must be unique
> accross all servers and database vendors. (I don't claim to be a
> database guru, so if we are all wet here please feel free to help
> correct our misunderstandings.)
I am not 100% sure, but I would believe that the
oid/uid/whatever_we_call_it only has to be unique within the table.
At least as long as you don't exchange data between different databases.
As soon as you transfer data from db a to db b, it's good to have an
object id that is unique in the world.
--
Reinhard Mueller
GNU Enterprise project
http://www.gnue.org
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
