| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Bill Moran <wmoran(at)potentialtech(dot)com>, "jerry(dot)evans(at)chordia" <jerry(dot)evans(at)chordia(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Analogue to SQL Server UniqueIdentifier? |
| Date: | 2008-02-19 20:54:12 |
| Message-ID: | 1203454452.5837.5.camel@mha-laptop.clients.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2008-02-19 at 11:07 -0500, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> >> Lack of support for Windows, which it sounds like the OP might be running?
>
> > That's something that's been on my agenda for a while. There are certainly
> > UUID generation functions available on Windows - at least for some of the
> > cases supported by uuid-ossp. If I were to write the same functions for
> > that one, where would people prefer that to go - in the uuid-ossp module
> > even though that's actually not correct (since it wouldn't be using ossp)
> > or a separate module uuid-win32?
>
> The latter is *completely* unacceptable. The entire point here is to
> not expose any differences at the SQL level.
>
> Why can't ossp be used --- is it impossible to port to Windows?
I haven't looked into the details - it's possible that it could be
portable to Windows. But that would a Yet Another Dependency to be bale
to build and run pg... So I'd like to avoid it if possible.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-02-19 21:34:57 | Re: Analogue to SQL Server UniqueIdentifier? |
| Previous Message | Dave Page | 2008-02-19 18:47:31 | Re: MS library files |