Skip site navigation (1) Skip section navigation (2)

Re: Re: New data type: uniqueidentifier

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Alex Pilosov <alex(at)pilosoft(dot)com>
Cc: "Dmitry G(dot) Mastrukov" <dmitry(at)taurussoft(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: New data type: uniqueidentifier
Date: 2001-07-03 15:33:09
Message-ID: Pine.LNX.4.30.0107031732400.677-100000@peter.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alex Pilosov writes:

> Dmitry's stuff contains both datatype (uniqueidentifier), a function to
> generate a new object of that type (newid), and a set of functions to
> implement comparison operators for that type.
> I don't see anything wrong with that setup, but maybe I'm still missing
> something?

It would be much simpler if you stored the unique id in varchar or text.

Peter Eisentraut   peter_e(at)gmx(dot)net

In response to


pgsql-hackers by date

Next:From: Martín MarquésDate: 2001-07-03 15:36:47
Subject: UNDO and partially commited transactions
Previous:From: Alex PilosovDate: 2001-07-03 15:20:33
Subject: Re: selecting from cursor

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group