Quote:
Originally Posted by Varius
Yup, this would be how to solve it.
Just find what's done to the text before it's inserted, then reverse that when it comes out. A BLOB field itself doesn't do its own encrypting or anything.
On the small chance there is nothing being done to the data before it's put into the database, check for any Triggers in MySQL as there could be one that ON INSERT or ON UPDATE encrypts the value in that field.
|
this is what it's doing when it processes a update/insert into that field.
$addtn = base64_encode(serialize($_POST['edit_add']));
$q = 'm_addtn="'.$addtn.'"'.$q;
i tried this piece of code (below) but just received a T_String error
print_r unserialize(base64_decode($results));