If you have trouble with duplicate OIDs
Please use patch-0.2 for testing. I have changed the OIDs to 5000 range.
You can download it from:
http://www.truesoftware.net/pgsql/uuid/patch-0.2/
On Mon, 2006-09-18 at 01:00 +0200, Gevik Babakhani wrote:
> Folks,
>
> The following patch implements the
Completely agreed. I can remove the function from the patch. The
temptation was just too high not to include the new_guid() in the
patch :)
On Mon, 2006-09-18 at 10:33 -0400, Tom Lane wrote:
> Andreas Pflug <[EMAIL PROTECTED]> writes:
> > Isn't guaranteed uniqueness the very attribute that's exp
Andreas Pflug <[EMAIL PROTECTED]> writes:
> Isn't guaranteed uniqueness the very attribute that's expected? AFAIK
> there's a commonly accepted algorithm providing this.
Anyone who thinks UUIDs are guaranteed unique has been drinking too much
of the kool-aid. They're at best probably unique. Som
Gevik,>uniqueness is never a guaranteed. that is according to the RFC docs.>uniqueness is never a guaranteed in the sense that there is a tiny>chance someone of the other side of the planet might generate the same
>guid. As much as I learned, it is recommended to give information about "grade of un
On Mon, 2006-09-18 at 09:21 +0200, Andreas Pflug wrote:
> Gevik Babakhani wrote:
> > - new_guid() function is supported. This function is based on V4 random
> > uuid value. It generated 16 random bytes with uuid 'variant' and
> > 'version'. It is not guaranteed to produce unique values
>
> Isn't
Gevik Babakhani wrote:
> - new_guid() function is supported. This function is based on V4 random
> uuid value. It generated 16 random bytes with uuid 'variant' and
> 'version'. It is not guaranteed to produce unique values
Isn't guaranteed uniqueness the very attribute that's expected? AFAIK
ther
