Received: from forward.airstreamcomm.net (forward.airstreamcomm.net [64.33.128.12]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9OHg7P81507 for ; Wed, 24 Oct 2001 13:42:07 -0400 (EDT) (envelope-from jghasler@svtel.net) Received: from hasler.dhh.gt.org (elk-ras1-cs-77.dial.airstreamcomm.net [64.33.137.79]) by forward.airstreamcomm.net (8.12.0/8.12.0) with ESMTP id f9OHfxkI007184 for ; Wed, 24 Oct 2001 12:41:59 -0500 (CDT) Received: from [192.168.1.3] (helo=toncho.dhh.gt.org ident=mail) by hasler.dhh.gt.org with esmtp (Exim 3.12 #1 (Debian)) id 15wS2R-0005Dh-00 for ; Wed, 24 Oct 2001 12:41:59 -0500 Received: from john by toncho.dhh.gt.org with local (Exim 3.12 #1 (Debian)) id 15wS1f-0006Ui-00; Wed, 24 Oct 2001 12:41:11 -0500 To: pgsql-sql@postgresql.org Subject: Re: GUID in postgres References: From: John Hasler Date: 24 Oct 2001 12:41:11 -0500 In-Reply-To: Message-ID: <87adyhx7ew.fsf@toncho.dhh.gt.org> Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200110/348 X-Sequence-Number: 5301 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 john@dhh.gt.org Dancing Horse Hill Elmwood, Wisconsin