For several reasons I would also vote for json_encode over serialize. Serialize is very sensitive when it comes to modifications on the serialized string. Use json instead. Current versions of database systems also support json as column type > Shawn McKenzie <shawn@xxxxxxxxxxxxx> hat am 14. November 2013 um 23:38 > geschrieben: > > > If you are for example saving the entire $_POST array in a text field of > your DB, then just serailize() it or json_encode() it and run it through > the appropriate real_escape_string() function if you're not using prepared > statements or other custom escaping. > > > On Thu, Nov 14, 2013 at 3:40 PM, Ramiro Barrantes < > ramiro@xxxxxxxxxxxxxxxxxxxxx> wrote: > > > Hello, > > > > I would like to record, on a database, the global variables $_POST and > > $_SERVER for each action that the user does that involves a modification of > > the database. I am just saving, say $_POST or $_SERVER (and others), as a > > string and putting it in a field on the database. > > > > However, when I try to get the info out of the database and access it as > > an XML (using the DOMDocument library) it becomes a pain to handle due to > > all the special characters (I think, as I haven't been able to get it to > > work), for example: > > > > Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 > > > > (I seem to need to replace all the "/"s) > > > > It's a pain, and I would like not to have to replace special characters > > with preg_replace if possible. > > > > Any suggestions? I have been having a lot of trouble with this. > > > > Thanks in advance, > > > > Ramiro > > > > -- Marco Behnke Dipl. Informatiker (FH), SAE Audio Engineer Diploma Zend Certified Engineer PHP 5.3 Tel.: 0174 / 9722336 e-Mail: marco@xxxxxxxxxx Softwaretechnik Behnke Heinrich-Heine-Str. 7D 21218 Seevetal http://www.behnke.biz -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
