aapeliv

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFt6Y6QBEAD8xUqVQiONPNcDe82OPYeFgjNzUMSgcTT/kePjyjjQwwTtaLJg
BawppXIQunejf34tTJgV4KsChjFYjeKUoPuleZksW2x8Dkq0gPznxmKNx2s3887p
E9N72xMacc7wpQYEQE+Y3wr7o+1+rBiv61jzXDMGIlMoUg0oG14RWOyzKLqr2tZm
aO1L7ty5dtzVxOntSY8WNzxb/m/ZKspP29EP3KW3MzE3TsoxLALqrEmxHs97gbxb
/cpkRZVLfBbG3AhCNUwxTYvZcdvgIMKndhLDvTu2h6W04lxRKr7UzdVoj+yk5t7t
R21T8PcfcdG+Dcm0XZDv1WooFjR3hjkStjf2eTrLJLGMhHxOkP+RQ8Rt76otsgOA
0z4XDANSxseyqA+aMERtTjCWZKHgB7GeMVMcJMZwa6M1pNlbTNbuFfK3quWAlOUa
sfKuqtFfz+ZqS39Wk0mdngnUmZ6rmo5hwbk0DFAvfxrH2uksEihEwgWklEEAf2wA

aapeliv

Keybase proof

I hereby claim:

• I am aapeliv on github.
• I am aapeli (https://keybase.io/aapeli) on keybase.
• I have a public key whose fingerprint is 0673 DC0F 553C 7FE3 680B 95DB 3F83 5A29 190C B0C2

To claim this, I am signing this object:

aapeliv

-- Sequential UUIDs in PostgreSQL
-- 
-- Afer ages of trying to figure this out (because apparently no one
-- needs sequential UUIDs), I finally figured out how to do this.
--
-- They aren't exactly UUIDs, according to the standard, but they are 
-- random 128 bit sequences that fit into the Postgres UUID type.
--
-- It's not good code and probably not very fast, but it's a good start.
--