On ðÔÎ, 2001-10-26 at 21:14, [EMAIL PROTECTED] wrote:
> Hi
>
> I think most of you are missing the point here.
>
I'm missing nothing :)
"uniqueidentifier" (128-bit unique value) data type fot PostgresSQL
exists and is used at least by me. It utilizes functionality of uuid
library from widely use
"Kaiserdigital":
> Why would you want to use two columns when you use could one? Two
> columns in each table would clutter your scheme as well as your
> procedures.
It's a relational integrity issue. A GUID, by definition, contains two
pieces of information:
1. The local primary key
2. The serv
e MAC into the GUID is
uniqueness between machines.
-Original Message-
From: Josh Berkus [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 26, 2001 11:31 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [SQL] GUID in postgres
Folks,
> I think most of you are missing t
Folks,
> I think most of you are missing the point here.
>
> GUIDs are unique and they are required for Enterprise development.
I don't know. I have yet to hear a persuasive argument as to why none
of the schemes previously mentioned would not work. While a "GUID"
automated by the RDBMS pla
Hi
I think most of you are missing the point here.
GUIDs are unique and they are required for Enterprise development.
For those of you who have used multi master replication on Oracle or MS
SQL, you know that identity columns and sequences are problematic. The
only way to work with primary key
On óÒÄ, 2001-10-24 at 09:55, Dinesh Parikh wrote:
> Hi,
> Is there any concept of sys_Guid in postgres.
> If yes what is that ??
> As i am using GUID in sql and oracle, then what is counterpart of this in postgres.
>It is urgent.
>
> Thanks in advance
> Bye
> Dinesh Parikh
>
Look at http://www
Horst,
> What we are using is the following:
> - All tables in need of a global ID _within_ a database inherit a
> globid
> table which contains nothing but an ID of type serial.
> - When we need cross-database unique IDs within the same system, the
> globid
> table contains a database identifi
I wrote:
> Globally Unique IDentifier, probably. Just hash a 128 bit random number
> with the current date.
Horst writes:
> That gives you no gurantee it will be unique.
There is no such guarantee. The probability of a collision due to errors
and bugs using a "deterministic" system is sure to
On Thursday 25 October 2001 03:41, John Hasler wrote:
> Josh writes:
> > I'm sure you could make your own GUID, whatever one is.
>
> Globally Unique IDentifier, probably. Just hash a 128 bit random number
> with the current date.
That gives you no gurantee it will be unique.
What we are using i
Josh writes:
> I'm sure you could make your own GUID, whatever one is.
Globally Unique IDentifier, probably. Just hash a 128 bit random number
with the current date.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
---(end of broadcast)
"Josh Berkus" <[EMAIL PROTECTED]> writes:
> Please do not cross-post to two different lists. It annoys those of us
> who are subscribed to both lists, and you are less likely to get help.
Just FYI, the Postgres mail server has a very nifty feature you can set
so that you get only one copy of cro
Dinesh,
Please do not cross-post to two different lists. It annoys those of us
who are subscribed to both lists, and you are less likely to get help.
> Is there any concept of sys_Guid in postgres.
> If yes what is that ??
> As i am using GUID in sql and oracle, then what is counterpart of
> t
12 matches
Mail list logo
