Re: Opinion wanted on UUID/GUID datatype output formats.

From: "Jim C(dot) Nasby" <jimn(at)enterprisedb(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Gevik Babakhani <pgdev(at)xs4all(dot)nl>
Subject: Re: Opinion wanted on UUID/GUID datatype output formats.
Date: 2006-09-16 23:37:34
Message-ID: 20060916233733.GJ38854@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 |
> > ----------------------------------+
> > 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 we want to have a formatting function to be able
> > to provide other common formats of the uuid/guid?
>
> If you stick to the standard format, I don't think that will be
> necessary.

+1. For people that care about the non-standard MSSQL format, they can
easily create their own function that will wrap it in {}.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gevik Babakhani 2006-09-16 23:47:48 Opinion about macro for the uuid datatype.
Previous Message Gregory Stark 2006-09-16 23:34:28 Re: The enormous s->childXids problem