After the change, cannot insert a value with a quote in it.

Now trying to edit the newly inserted row containing a quote, in the "showing rows" box I get Array Array.

Rabus wrote: Reproduceable on our demo at phpmyadmin.net, see table "marc".

Alexander, in version 2.4.0, I would get this output from the pretty parser showing the UPDATE statement: UPDATE `marc` SET `c1` = 'L\'amie\'' WHERE `c1` = 'L\'amie' LIMIT 1 and this, for the following SELECT: SELECT * FROM `marc` In current 2.4.1-dev, I get this: UPDATE `marc` SET `c1` = 'L'amie'' WHERE `c1` = 'L'amie' LIMIT 1; with no pretty colors. Note the unescaped quotes. And then, calling again the parser in common.lib.php3 line 1297, makes the parser choke. $GLOBALS['SQP_errorString'] contains the error message for unbalanced quote, but the error message is not shown, instead Array Array is displayed. Marc What happens is that Rabus wrote: > Hi Marc & list, > > -----Original Message----- > From: Marc Delisle [mailto:delislma@CollegeSherbrooke.qc.ca] > >> Rabus wrote: >> >> >>> Hi Marc & list, >>> >>> -----Original Message----- >>> From: Marc Delisle [mailto:DelislMa@CollegeSherbrooke.qc.ca] >>> >>>> Now trying to edit the newly inserted row containing a >>>> quote, in the "showing rows" box I get Array Array. >>>> >>>> >>> I cannot reproduce this issue. Editing rows works fine here, with >>> magic_quotes_gpc as well as without. >>> >> Reproduceable on our demo at phpmyadmin.net, see table "marc". >> >> > > I exported your table, tried it on my machine and got the same error > here. > > I noticed that, in the first box, the pretty-printer appears to be > deaktivated automatically somehow. > It seems as if the query of the second box has been parsed (the parser > returns an array with the tokenized query), but hasn't been passed to > the pretty-printer afterwards. > > Robin, since you know your code better than me, could you help me with > that? I don't want to break more than I already have... > > Regards, > > Alexander M. Turek > <alex(a)bugfixes.info>