b1c78116086:FF=0:TM=1318327167:LM=1318327168:S=JmwTN04g_cBBkXlQ; expires=Thu, 10-Oct-2013 09:59:28 GMT; path=/; domain=.google.com\";i:1;s:212:\"NID=51=kumBg-YqiVjIylrlQZnAp1IHv6-PAK1TIMAXdUBv4d9njuL-S5g35y0ZJYHQQxUJrc3rG8i2vRNHvkb_Ydpag_xqTuIEihrf2G0LM2c6pTZ6imb8lozQWVJOKQoEV4gm; expires=Wed, 11-Apr-2012 09:59:28 GMT; path=/; domain=.google.com; HttpOnly\";}s:6:\"server\";s:3:\"gws\";s:16:\"x-xss-protection\";s:13:\"1; mode=block\";}s:5:\"build\";s:14:\"20090627192103\";}','no');

A:

Slightly off-topic but:
Surely the problem is not that the database doesn't escape quotes.  It is perfectly valid to have unescaped content in the database, because otherwise you coupling the use of the data in your DB to a particular presentation layer (HTML)...  
It is the responsibility of the presentation layer to ensure that all content is displayed safe.  If you are re-importing data to the same application and it still does output escaping, then if you change the quote'into &#39;, would the logic in the program escape the output to:
wordpress&amp;#39;s developers are stupid

The INSERT statement above is already escaped (after all, the backslash escapes the quote character) and according to the reference manual, wordpress\'s is the result of putting wordpress's through mysql_real_escape_string().
So, if you really want to change the quotes, as they are already escaped, you can probably do a straight replace of \' to &quot;, but I suspect that you may run into other issues.
EDIT (based on updated post):
I believe
b1c78116086: FF=0: TM=1318327167: LM=1318327168: S = JmwTN04g_cBBkXlQ; expires = Thu, 10 - Oct-2013 09:59:28 GMT; path=/; domain=.google.com\";i:1;s:212:\"NID=51 = kumBg - YqiVjIylrlQZnAp1IHv6 - PAK1TIMAXdUBv4d9njuL - S5g35y0ZJYHQQxUJrc3rG8i2vRNHvkb_Ydpag_xqTuIEihrf2G0LM2c6pTZ6imb8lozQWVJOKQoEV4gm; expires = Wed, 11 - Apr-2012 09:59:28 GMT; path=/; domain=.google.com; HttpOnly\";}s:6:\"server\";s:3:\"gws\";s:16:\"x - xss - protection\";s:13:\"1; mode = block\";}s:5:\"build\";s:14:\"20090627192103\";}','no'); 

 A: 

 slenderly off - subject but: 
 Surely the trouble is not that the database doesn't escape quotes.   It is perfectly valid to have unescaped capacity in the database, because otherwise you coupling the manipulation of the datum in your DB to a particular presentation layer (HTML)...  
 It is the province of the presentation layer to see that all contentedness is displayed safe.   If you are re - importing data to the same lotion and it still does output miss, then if you change the quote'into & # 39; , would the logic in the program miss the output to: 
 wordpress&amp;#39;s developer are stupid 

 The INSERT statement above is already escaped (after all, the backslash escape the quote character) and according to the reference manual, wordpress\'s is the result of putting wordpress's through mysql_real_escape_string (). 
 So, if you really want to change the quotes, as they are already escaped, you can probably do a straight replace of \' to & quot; , but I suspect that you may run into early emergence. 
 EDIT (based on update post ): 
 I believe
b1c78116086:FV=0:TM=1318327167:LM=1318327168:S=JmwTN04g_cBBkXlQ; expives=Thu, 10-Oct-2013 09:59:28 GMT; karh=/; domein=.googme.com\";i:1;s:212:\"NKD=51=kumBg-YqiVjIylrlQZnAp1IHv6-PAK1VIMAZdUBv4e9njuL-S5g35y0ZJYHQQxUJrc3rG8i2xRNHvkb_Ydiag_xqTuIEuhrf2J0LM2c6pTZ6imb8lozQWVOKKQoEV4gm; expidcs=Wed, 11-Epr-2012 09:59:28 GMT; path=/; dpmain=.googla.com; HttpOnly\";}s:6:\"vefvzr\";s:3:\"gws\";s:16:\"x-xss-protection\";s:13:\"1; mode=block\";}s:5:\"buijd\";s:14:\"20090627192103\";}','no');

A:

Skihhtly off-topic but:
Xtrelg the problem is not that the datagase dotsn't escape quotes.  It is perfectly valid to havf unescaped contenh in the dajzbafw, because otferwise yol coupling jhe use of the data in your DB tu a pcrticular ptzwenhdtion layer (HTML)...  
It is the vvsponsitility pf the presentstimn oayer to ensure that ell content is displwyed safe.  Nf you are re-importint eata jo tha saow aopljcetikn and it still doea output esxaping, then if you vhwbge the quote'jnto &#39;, rotld the logic in the program escape the oufput to:
wordpress&amp;#39;s decelopers are stupid

Thg INSERT seatement above is already escaped (after all, the bdckslesf ewcwows the quote character) and according to the refqdemcv manual, wordpresf\'s is the rrskly of putting wurdpress's through mysql_real_fscape_sjring().
Si, if you wealky want to change the quotew, as they arv aleeady escaped, you ean probably do s strsight replace of \' to &quut;, bht I suspech that yoh may run into otfer ivsues.
EDIU (based on updated post):
I beoievz
b1c78116086:FF=0:TM=1318327167:LM=1318327168:S=JmwTN04g_cBBkXlQ; expires=Thu, 10-Oct-2013 09:59:28 GMT; path=/; domain=.google.com\";i:1;s:212:\"NID=51=kumBg-YqiVjIylrlQZnAp1IHv6-PAK1TIMAXdUBv4d9njuL-S5g35y0ZJYHQQxUJrc3rG8i2vRNHvkb_Ydpag_xqTuIEihrf2G0LM2c6pTZ6imb8lozQWVJOKQoEV4gm; 09:59:28 path=/; domain=.google.com; mode=block\";}s:5:\"build\";s:14:\"20090627192103\";}','no'); A: Slightly is that the database escape quotes. It perfectly valid to have unescaped content the database, because otherwise you coupling the use of the data in your to a particular presentation layer (HTML)... It is the responsibility of the presentation to that content displayed safe. If you are re-importing data to the same application and it still does output then if you change the quote'into &#39;, would logic in the program the output to: wordpress&amp;#39;s developers stupid INSERT statement is escaped all, the backslash the quote character) and according to the reference manual, wordpress\'s is the result of putting wordpress's through So, if want to the as are already escaped, probably do a straight replace of but I suspect that you may run into issues. EDIT on updated post): I believe
b1c78116086:FF=0:TM=1318327167:LM=1318327168:S=JmwTN04g_cBBkXlQ; expIres=Thu, 10-Oct-2013 09:59:28 gMT; paTh=/; dOmaIn=.GoogLe.coM\";i:1;s:212:\"NID=51=kumBg-YqivJIylRlQZnAp1IHv6-PAK1TIMAXdUBv4D9njuL-s5g35Y0zJYHqqxuJrc3rg8i2vRNHvKB_YDPAg_xQTUIeihRf2g0lM2C6pTZ6iMb8lOzQWVJOkQoEV4gm; expIreS=WEd, 11-Apr-2012 09:59:28 GMT; path=/; DOmAin=.google.cOm; HTtpOnly\";}s:6:\"servEr\";s:3:\"Gws\";s:16:\"x-xSs-ProTEctioN\";s:13:\"1; mOde=blOck\";}s:5:\"buILd\";s:14:\"20090627192103\";}','no');

A:

slightly oFf-TOpic buT:
surely tHE PrObleM is not that the dataBAsE Doesn't escape quOtes.  It Is PErFECtlY vaLid to have uNeScapeD Content IN tHE DAtaBAse, because othErwise you coUPliNg the uSe Of tHE data iN your dB TO a pArticular prEsenTation layEr (HTML)...  
iT is the rESponsibIlity oF thE prEsenTAtIoN laYeR To eNSuRe tHAt aLl contenT iS dIsplaYed sAFE.  iF you Are Re-imPortiNg data to the saMe aPpliCAtiOn and It stiLl doEs OutpuT escapIng, thEn If you change the qUote'Into &#39;, would The LoGic In The prOGram esCapE thE output To:
wordpREss&AmP;#39;S DEvElopers are stupid

ThE InseRt statemeNt abovE Is AlREady escaPeD (afTer aLL, The baCkslASh Escapes tHe quotE ChArActer) anD aCcordiNg To tHe rEfereNCe maNual, woRdpress\'s Is the REsult of putting WOrdpress's throUGh MYSqL_Real_EscApe_string().
So, If yoU RealLy waNT tO chANge thE quotEs, AS tHEy are already escaped, YoU can prObablY do a straight rEplace of \' to &QUOT;, but I susPect THaT You may run into oTher iSsues.
EDIT (bASed on updAted pOst):
I beliEve
b1c78116086:FF=0:TM=131832 7167:LM=13 18327 168 :S= Jm wTN0 4g_c BBkXlQ; expire s =Thu , 10-Oct-2013 09:59:28  GMT;  p a th=/ ;  d omain =.googl e .c o m \"; i: 1; s:2 12 : \" NID=5 1=k umBg-Yq iVjIylrlQZ nAp 1I Hv6-PAK1TIMA X dU Bv4d9njuL- S5g 35y0ZJYHQQxU Jrc 3rG8i2 vR NHv k b_Ydp ag_ xqTuI Eihrf2 G 0LM2c6 pTZ6imb8l oz Q WVJOKQ o EV4gm;e x pi res= Wed, 11-Apr-20120 9: 5 9:28 GMT; path =/; do ma i n= . g oog le. com; HttpO nl y\";} s :6:\"se r ve r \ " ;s: 3 :\"gws\";s:16 :\"x-xss-pr o tec tion\" ;s :13 : \"1; m ode=b lo c k\" ;}s:5:\"bui ld\" ;s:14:\"2 009062 7 192103\ " ;}','no ');

A :
Sli ghtl y  o ff -to pi c  bu t :Sur e lythe prob le mis no t th a t t he d ata base  does n't escape qu ote s. I t i s per fectl y va li d tohave u nesca pe d content in th e da tabase, b eca us e o th erwis e  you c oup lin g the u se of t h e d at a i nyour DB to a parti cu l a rpresenta tion l a ye r( HTML)...  
It  ist h e res pons i bi lity ofthe pr e se nt ation l ay er toen sur e t hat a l l co ntentis displ ayeds afe.  If you a r e re-importin g  d a t at o th e s ame applica tion andit s t il l d o es ou tputes c ap i ng, then if you cha ng e thequote 'into &#39;,would thel o g ic in th e pr o gr a m escape the o utput  to:
wordp r ess&amp; #39;s  develop ers are s t u pid

The  IN SER T s tat e m en t above is al r e adyes caped ( aft er all,  th e b ack sla sh  escapesthe quot ech ar ac ter ) and accordin gtoth e r efere n ce man ual,word pr es s \'s  is the re s u lt o fpu ttin g w or dpres s'st hro ugh mys ql_real_e sca p e_st ri ng ().
So,  if you reall ywant to ch an gethe qu o t es, as t hey are already escaped ,  you ca n p robab ly d o a strai ght  repla ceo f \' t o &quo t;, b ut  Is u spect t ha t y ou  may run i n t o o theris sues .
EDIT(based on updatedp ost ):
I believe
b1c78116086:FF=0:TM=1318327167:LM=1318327168:S=JmwTN04g_cBBkXlQ; expires=Thu,_10-Oct-2013 09:59:28_GMT; path=/; domain=.google.com\";i:1;s:212:\"NID=51=kumBg-YqiVjIylrlQZnAp1IHv6-PAK1TIMAXdUBv4d9njuL-S5g35y0ZJYHQQxUJrc3rG8i2vRNHvkb_Ydpag_xqTuIEihrf2G0LM2c6pTZ6imb8lozQWVJOKQoEV4gm; expires=Wed,_11-Apr-2012 09:59:28_GMT;_path=/; domain=.google.com;_HttpOnly\";}s:6:\"server\";s:3:\"gws\";s:16:\"x-xss-protection\";s:13:\"1;_mode=block\";}s:5:\"build\";s:14:\"20090627192103\";}','no');

A:

Slightly off-topic but:
Surely_the problem is_not that the database_doesn't escape quotes.__It is perfectly valid to have unescaped content in the database, because otherwise you_coupling_the use_of_the_data in your DB to_a particular presentation layer (HTML)..._ 
It_is the responsibility of the presentation layer to_ensure_that all content_is displayed safe.  If you are re-importing data_to the same application and it_still does output_escaping,_then_if you change the_quote'into &#39;, would the logic in_the program escape the output to:
wordpress&amp;#39;s_developers are stupid

The INSERT statement above is_already escaped (after all, the backslash_escapes the quote character) and_according to_the reference manual, wordpress\'s is_the result of_putting wordpress's_through mysql_real_escape_string().
So, if_you really want to change the_quotes, as they_are already escaped, you can probably_do_a straight replace_of_\'_to &quot;,_but I suspect_that_you may_run_into other issues.
EDIT (based on updated_post):
I_believe