From: | "Dawid Kuroczko" <qnex42(at)gmail(dot)com> |
---|---|
To: | "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | UUID data format 4x-4x-4x-4x-4x-4x-4x-4x |
Date: | 2008-02-27 23:15:00 |
Message-ID: | 758d5e7f0802271515q432b00f6l15cbf0cdf5c73e1b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello.
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
replace(text,'-','')::uuid for
this kind of data.
Nooow, the case is quite simple and it might be that there are other
applications
formatting UUIDs too liberally.
I am working on a patch to support this format (yes, it is a simple
modification).
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. [1] While good
applications format
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?
Regards,
Dawid
[1]: 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2008-02-27 23:54:05 | Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x |
Previous Message | Tom Lane | 2008-02-27 22:48:53 | Re: Idea for minor tstore optimization |