Hi Chris,
I remember that article, I think I saw it on PlanetMySQL.com -- but I
can't find it either. I do remember that it encrypted the column
putting it into the database, and used a VIEW to decode it, and then
limited the access to the view.
Hope that helps!
-Sheeri
On 2/23/06, [EMAIL PROT
When 5.0 came out, I saw an article or white paper or something with an
example of a stored procedure (I think, maybe a trigger) that allowed
you to transparently encrypt a column so that even if a database backup
was stolen, that column wouldn't be exposed to the thieves. I believe
that the examp
