Basically he is rolling his own crypto. Far better advices are the possibilities given in https://wiki.postgresql.org/wiki/Pseudo_encrypt (skip32 and xtea) which has not constant key. If one has to keep existent key, one could use two different prefix for old and new key.
Basically he is rolling his own crypto. Far better advices are the possibilities given in https://wiki.postgresql.org/wiki/Pseudo_encrypt (skip32 and xtea) which has not constant key. If one has to keep existent key, one could use two different prefix for old and new key.
The 32bit version from the postgresql site:
https://wiki.postgresql.org/wiki/Pseudo_encrypt
Looks like a great approach for this problem and will outperform using UUIDs.