Marco,

> Maybe storing it into a CHAR(22) using OCTECTS charset?

While this will work and is the smallest storage footprint/representation.

I would recommend to sacrifice disk space and to store the key as a string 
using a base 36 encoding (0-1 + A-Z) -- it makes debugging via tools much 
easier.  Difference space between OCTET and base 36 encoding would only be an 
additional 7 characters.


Sean

Reply via email to