Thanks Jonthan. However, I wonder how an md5 string can be squeezed into a 10, or even 6-character field with no concern of (future) collision -- or am I mis- understanding your db schema?
Sincerely, Jerry On Jul 5, 1:57 pm, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: > On Jul 4, 8:58 pm, jerry <[EMAIL PROTECTED]> wrote: > > > But how? What encryption/hashing method could be used to transform the > > numeric IDs to something less obvious? > > all my apps have somthing like this in the db: > > table hexkey_types > id , len , name > --- > 1, 10, useraccount:hex_id > 2, 6, group:hex_id > 3, 6, assetname:hex_id > > table hexkey > hex_id primary, hexkey_type (fkey on hexkey_type(id)) > > table useraccount > id , hex_id fkey on hexkey10 > > i just create random md5s whenever i make an entry into the db. > > when someone requests i record, i validate to make sure the hexid > matches for the function ( are we requesting a 10char hex for a user? > if so check memcached with db failover. if not , then don't > bother ). storing a hex-to-numeric mapping in memcached makes it > really low-impact. and no one knows what my internal mappings are. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
