> The dashless format is neither standards compliant nor compatible with
> other databases that have uuid functions (notably MS SQL Server and
> MySQL), nor with microsoft tools where they're used frequently.
> (ignoring the {} wrapping stuff which is trivial).
>
> If we add a UUID type to core
devdb=# select * from tbluuid;
pk|
--+
6b13c5a1afb4dcf5ce8f8b4656b6c93c |
01e40a79b55b6e226bffb577e960453d |
(2 rows)
The UUID standards define a single perfectly clear format, and the one
you show is not it.
I was wondering if
On Thu, Sep 14, 2006 at 11:32:09PM +0200, Peter Eisentraut wrote:
> Gevik Babakhani wrote:
> > As suggested in earlier discussion we provide a raw/plain output of
> > the uuid type:
> >
> > devdb=# select * from tbluuid;
> > pk|
> > --
Gevik Babakhani wrote:
> As suggested in earlier discussion we provide a raw/plain output of
> the uuid type:
>
> devdb=# select * from tbluuid;
> pk|
> --+
> 6b13c5a1afb4dcf5ce8f8b4656b6c93c |
> 01e40a79b55b6e226bffb577e960453d |
>
Gevik,
> select format_uuid(mypk,'format3') from tbluuid;
> and then get: {6b13c5a1-afb4-dcf5-ce8f-8b4656b6c93c}
> (which would be MSSQL compatible)
> What do the PostgreSQL masters think? :)
There are no masters here. Except in replication.
I think that we should have a formatting function,
On 9/14/06, Gevik Babakhani <[EMAIL PROTECTED]> wrote:
At this moment we (almost) have a uuid/guid datatype.
As suggested in earlier discussion we provide a raw/plain output of the
uuid type:
devdb=# select * from tbluuid;
pk|
--+
> select format_uuid(mypk,'format2') from tbluuid;
> and then get: 6b13c5a1-afb4-dcf5-ce8f-8b4656b6c93c
How about instead of fixed formats, you allow a format string using the
diverse parts of the GUID a la time formatting functions ? Then
everybody can format it as they want.
Just an idea.
Chee
