| From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
|---|---|
| To: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: (psuedo) random serial for PK or at least UNIQUE NOT NULL? |
| Date: | 2010-05-05 11:01:49 |
| Message-ID: | u2ue94e14cd1005050401k27cdd9f9l3a829f9f1738cbaf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2010/5/5 Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>:
>>>>>>> http://wiki.postgresql.org/wiki/Pseudo_encrypt
>>> That's a nice starting point.
>>> I should apply that function twice for each 32-bit chunk of a
>>> 64-bit BIGINT and then merge the results into a single BIGINT ...
>>> Boring but doable!
>>
>> Hum, not sure. If I understand correctly, you won't be able to get the
>> original int64 from the generated one.
>
> Why should I bother?
Dunno, but it was in the original spec.
>
>> Better rewrite the function for 2^64 isn't it ?
>
> Sure!.
>
> --
> Vincenzo Romano
> NotOrAnd Information Technologies
> NON QVIETIS MARIBVS NAVTA PERITVS
>
--
Cédric Villemain
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Schuchardt | 2010-05-05 11:23:59 | dynamically access columns in trigger |
| Previous Message | Vincenzo Romano | 2010-05-05 10:46:31 | Re: (psuedo) random serial for PK or at least UNIQUE NOT NULL? |