Right now mysql's SHA1 implementation uses Base16 encoding...
Why not add a Base64+filesafe encoding. This results in significant space storage. Maybe call the function SHA1BASE64()
Example:
Base64+filesafe(SHA1): C-7Hteo_D9vJXQ3UfzxbwnXaijM
Base64(SHA1): C~7Hteo-D9vJXQ3UfzxbwnXaijM
Base32(SHA1): BPXMPNPKH4H5XSK5BXKH6PC3YJ25VCRT
Base16(SHA1): 0beec7b5ea3f0fdbc95d0dd47f3c5bc275da8a33
Base64+filesafe is just an encoding that removes / and other chars that can't be in URLs and filenames.
I don't know about you but I like my database as less bloated as possible ;)
Kevin
--
Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat.
Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html
If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll
get a free iPod!
Kevin A. Burton, Location - San Francisco, CA
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
