> > This is not really a viable replacement for a GUID == > globally unique > > identifier. Here global means that if I use the application in > > multiple databases, I'm guaranteed that no two identifiers > will be the > > same. Using a sequence will only support uniqueness for a single > > database. > > So, how can two databases, not currently talking to one > another, guarantee that their GUIDs don't collide? using a > large randomly generated name space only reduces the chances > of collision, it doesn't actually guarantee it.
At least on Windows, the GUID is derived in part from the computers primary MAC address. No, it's not a guarantee, but it's pretty unlikely :-) //Magnus ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
