Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 70C902E2F57 for ; Tue, 12 Feb 2008 06:14:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 07919-03-7 for ; Tue, 12 Feb 2008 06:14:34 -0400 (AST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id 37EBD2E0CD9 for ; Tue, 12 Feb 2008 05:05:43 -0400 (AST) Received: (qmail 21482 invoked by uid 0); 12 Feb 2008 09:05:41 -0000 Received: from 193.171.152.33 by www154.gmx.net with HTTP; Tue, 12 Feb 2008 10:05:41 +0100 (CET) Cc: pgsql-sql@postgresql.org Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Feb 2008 10:05:41 +0100 From: "Sven Sporer" In-Reply-To: <3844.1202751300@sss.pgh.pa.us> Message-ID: <20080212090541.76470@gmx.net> MIME-Version: 1.0 References: <20080211102557.118950@gmx.net> <2916.1202748993@sss.pgh.pa.us> <20080211170412.GB13934@alvh.no-ip.org> <3844.1202751300@sss.pgh.pa.us> Subject: Usage of UUID with 8.3 (Windows) To: Tom Lane X-Authenticated: #20921651 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19FdRA1SDBFqWthT+u6BEqY25rKO9kSPY/ClzWnt2 VYaTo1of4wk4+6MhFhsB7hmKEycJk6aBJq6A== Content-Transfer-Encoding: 7bit X-GMX-UID: VFOXb/a6Li50NhsZVWppW2prZml1ZFhL X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.101 tagged_above=0 required=5 tests=AWL=0.100, BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200802/90 X-Sequence-Number: 30181 > > I think Windows has its own UUID generator, so the best bet would be to > > make that work. > > Only if it can be made to present the same SQL-level API as we have for > OSSP. Otherwise we'll be faced with boatloads of platform-dependent > client code ... I'm just curious, but why aren't those features included in the Windows version in order to prevent platform-dependent development in that direction? The same Postgres version now essentially provides different features depending on the platform. I understand now that you just want to provide the facilities for UUID handling (datatype). You have to agree that a function to create a v4 UUID based on a randomly generated number (see MySQL: UUID()) would be useful though.