I am currently playing with UUID data type and try to use it to store provided
by third party (Hewlett-Packard) application. The problem is they
format UUIDs as
0000-0000-0000-0000-0000-0000-0000-0000, so I have to
this kind of data.
Nooow, the case is quite simple and it might be that there are other
formatting UUIDs too liberally.
I am working on a patch to support this format (yes, it is a simple
And in the meanwhile I would like to ask you what do you think about it?
Cons: Such format is not standard.
Pros: This will help UUID data type adoption.  While good
their data well, there are others which don't follow standards. Also
I think it is
easier for a human being to enter UUID as 8 times 4 digits.
Your thoughts? Should I submit a patch?
: My first thought when I received the error message was "hey! this
is not an UUID,
it is too long/too short!", only later did I check that they just
don't format it too well.
pgsql-hackers by date
|Next:||From: Josh Berkus||Date: 2008-02-27 23:54:05|
|Subject: Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x|
|Previous:||From: Tom Lane||Date: 2008-02-27 22:48:53|
|Subject: Re: Idea for minor tstore optimization |