Re: Proposal for GUID datatype - Mailing list pgsql-hackers

From Thomas Hallgren
Subject Re: Proposal for GUID datatype
Date
Msg-id 45057B33.4030708@tada.se
Whole thread Raw
In response to Re: Proposal for GUID datatype  (Jan de Visser <jdevisser@digitalfairway.com>)
Responses Re: Proposal for GUID datatype  (Jan de Visser <jdevisser@digitalfairway.com>)
List pgsql-hackers
Jan de Visser wrote:
> On Friday 08 September 2006 15:18, Gevik Babakhani wrote:
>> 2a) Three input formats are supported.
>> example:
>> insert into tbl (fld) values('1dfb39af-b56a-40b8-a903-b5b31567c3ce');
>> insert into tbl (fld) values('{1dfb39af-b56a-40b8-a903-b5b31567c3ce}');
>> insert into tbl (fld) values('1dfb39afb56a40b8a903b5b31567c3ce');
> 
> Please extend your list. java's RMI package generates UIDs with the following 
> format:
> 
> [head order 21:19]$ bsh.sh
> BeanShell 1.3.0 - by Pat Niemeyer (pat@pat.net)
> bsh % print(new java.rmi.server.UID());
> 3b732da7:10d9029b3eb:-8000
> bsh %                                                                  
> 
> So forms that use colons instead of dashes seem appropriate.
> 
> Or better still, make it configurable.
> 
> jan
> 
RMI UID's has nothing in common with UUID's so I fail to see how they 
have any relevance here. I've never seen any other representation of the 
UUID's that the two that Gevik wants to support. Please note that UUID 
is a very well known concept and not an arbitrary 128 bit storage.

http://en.wikipedia.org/wiki/UUID is a good source of information. The 
appointed RFC actually contains source code.

Kind Regards,
Thomas Hallgren


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Fixed length data types issue
Next
From: Jan de Visser
Date:
Subject: Re: Proposal for GUID datatype