I have implemented GUID's in an application that needed them. We needed globally unique PK's and although Postgres did not offer them as a datatype, we used C# to perform that function. The Postgres database attribute ended up being a varchar(39). Not as performant as having Postgres natively do
On Jun 26, 2006, at 9:05 AM, Dennis Wagner wrote:
I'm currently thinking about using GUIDs as primary keys.
Look on pgFoundry.org; I'm pretty sure there's some kind of UUID type
there.
--
Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED]
Pervasive Software http://pervasive
> By its definition, GUID (
http://en.wikipedia.org/wiki/GUID ) is not> guaranteed to be unique. As a result, it could cause problems in> tables that have a large number of rows - actually this could result> in hard to reproduce, seemingly random errors in your systems that use
> the database. H
By its definition, GUID ( http://en.wikipedia.org/wiki/GUID ) is not
guaranteed to be unique. As a result, it could cause problems in
tables that have a large number of rows - actually this could result
in hard to reproduce, seemingly random errors in your systems that use
the database. How
By its definition, GUID ( http://en.wikipedia.org/wiki/GUID ) is not guaranteed to be unique. As a result, it could cause problems in tables that have a large number of rows - actually this could result in hard to reproduce, seemingly random errors in your systems that use the database. How does
