Weblog entry #168 for simonw
#168
Dreamweaver with PHP error
Posted by simonw on Wed 9 May 2007 at 15:45
Error:
"While executing onChange in ServerObject-InsRecPHP.htm a Javascript error occurred."
Tracked to a database column in MySQL with the name "length".
Took too much time to find it, and searching was less productive than expected.
I can't image how having a column called length causes Dreamweaver a problem ;)
"While executing onChange in ServerObject-InsRecPHP.htm a Javascript error occurred."
Tracked to a database column in MySQL with the name "length".
Took too much time to find it, and searching was less productive than expected.
I can't image how having a column called length causes Dreamweaver a problem ;)
Comments on this Entry
Posted by Anonymous (213.164.xx.xx) on Thu 10 May 2007 at 11:48
It's a reserved word.
[ Parent | Reply to this comment ]
I saw that in one place, but it is not listed here;
http://dev.mysql.com/doc/refman/5.0/en/reserved-words.html
Besides even if it were reserved, I'd still be able to use it with appropriate quoting within MySQL.
http://dev.mysql.com/doc/refman/5.0/en/reserved-words.html
Besides even if it were reserved, I'd still be able to use it with appropriate quoting within MySQL.
[ Parent | Reply to this comment ]
Posted by Anonymous (213.164.xx.xx) on Fri 11 May 2007 at 12:50
[ Parent | Reply to this comment ]
That is a Javascript reserved word, I'm writing MySQL and PHP.
Anything not coping with valid MySQL and PHP is due to bugs in the Dreamwaver extensions. It is only incidental to my purposes that Dreamweaver happens to have some extensions written in Javascript.
They are presumably incorrectly handling the data somewhere - which I assume is probably an exploitable bug in their code. But life is too short to sniff down the bugs in proprietary software products.
Anything not coping with valid MySQL and PHP is due to bugs in the Dreamwaver extensions. It is only incidental to my purposes that Dreamweaver happens to have some extensions written in Javascript.
They are presumably incorrectly handling the data somewhere - which I assume is probably an exploitable bug in their code. But life is too short to sniff down the bugs in proprietary software products.
[ Parent | Reply to this comment ]