[EMAIL PROTECTED] wrote:
... I *like* sorting by time, as it allows
the UUID to be used similar to sequence, leaving older, lesser accessed
UUIDs in the past.
and don't forget, an automatic timestamp of when a record is created might be useful for
other purposes.
Regards,
Thomas Hallgren
-
> On Sat, Sep 09, 2006 at 07:47:19PM +0200, Aleksandar Dezelin wrote:
>> Using time based GUIDs in database tables is not a good choice for
>> performance reasons because they can not be indexed properly - every newly
>> created time-based GUID is guaranteed to be larger than all previously
>> crea
On Sat, Sep 09, 2006 at 07:47:19PM +0200, Aleksandar Dezelin wrote:
> Hello,
> you just have to make random 128 bits and set version bits. And that's all.
> This is the way this data type is implemented in Mono
> (http://svn.myrealbox.com/source/trunk/mcs/class/corlib/System/Guid.cs).
>
> Using t
Hello, you just have to make random 128 bits and set version bits. And that's all. This is the way this data type is implemented in Mono (
http://svn.myrealbox.com/source/trunk/mcs/class/corlib/System/Guid.cs). Using
time based GUIDs in database tables is not a good choice for
performance reasons
> Do you really want to copy the code verbatim? I mean, there's a lot of
> stuff which would need quite a bit of massaging to get working in
> postgres. I'd say just look at it, understand it, and then write
> something that will work. The copyright won't matter then.
>
This is a better idea i m
On Tue, Sep 05, 2006 at 02:29:15PM +0200, Gevik Babakhani wrote:
> For developing the GUID datatype, I was wondering if I could use the
> sample code from http://www.ietf.org/rfc/rfc4122.txt (hate to reinvent
> the wheel)
>
> The code has a copyright which says: "use and modify as you wish but
> i
For developing the GUID datatype, I was wondering if I could use the
sample code from http://www.ietf.org/rfc/rfc4122.txt (hate to reinvent
the wheel)
The code has a copyright which says: "use and modify as you wish but
include the copyright notice with your code"
What are our rules is such matte
On Tue, Sep 05, 2006 at 11:29:40AM +0200, Gevik Babakhani wrote:
> I have two questions regarding the GUID todo item...
>
> 1. Do we want to have a new datatype for that or just a macro like the
> SERIAL type?
A new datatype. Just because someone has a guid column doesn't mean
they want it autog
I have two questions regarding the GUID todo item...
1. Do we want to have a new datatype for that or just a macro like the
SERIAL type?
create table bla
(
my_pk GUID /* that is my_pk varchar(32) DEFAULT 'new_guid()' */
)
2. Didn't we have a contrib module doing the GUID?
Regards,
Gevik.
