| From: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com> |
| Subject: | Re: guid/uuid datatype |
| Date: | 2007-01-20 11:59:40 |
| Message-ID: | 1169294380.9447.10.camel@voyager.truesoftware.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
>
> But does it really help if you don't have the generator?
>
> I don't use UUIDs much myself, but I think in all cases I've seen that
> use the uuid type in SQL Server they're also using the generator function.
> Those that just store UUIDs in the database often just uses varchar - in
> order to be more portable, I guess.
>
There could be many algorithms to generate a guid. I guess we will get
into a big debate on that, which is not much useful i guess (seeing the
posts last year).
In most cases I have seen the guid is generated by the client. In case
of M$ Sql is also can be generated on the server but, in our case we
generate the guids ourselves because with our algorithm we can trace the
guid back to where it exactly was originated. (app requirement)
One thing is for sure, having varchar to store guids ( varchar(32) ) is
not that efficient.
Regards,
Gevik.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-01-20 12:15:45 | Re: guid/uuid datatype |
| Previous Message | Magnus Hagander | 2007-01-20 11:19:59 | Re: guid/uuid datatype |