Hi Noah Romer,
I got the same problem as yours. I think some of the "words" or "variables"
can't be used in MySQL-3.23.32 as in the previous version of MySQL-3.22.xx. The only
think you have to do is to change the "variables" in 3.23.32. In your case, may be
who or when is not allowed to
Ok, being careful to try and avoid any naughty words that might trigger the
bleeding spam filter.
The Tilghman wrote:
>
> 'when' is a reserved word in 3.23
Well, that would explain that. Arrrgghh! I even spent a couple of hours going
through the "upgrading from 3.22"/"major new features of 3.23
On Fri, Feb 02, 2001 at 03:38:09PM -0500, Noah Romer wrote:
> mysql> insert into bugs_activity (bug_id,who,when,field,oldvalue,newvalue)
> values (334,18,20010131145149,'bug_status','NEW','RESOLVED');
> ERROR 1064: You have an error in your SQL syntax near
> 'when,field,oldvalue,newvalue) values
>
> "NR" == Noah Romer <[EMAIL PROTECTED]> writes:
mysql> insert into bugs_activity (bug_id,who,when,field,oldvalue,newvalue)
NR> values (334,18,20010131145149,'bug_status','NEW','RESOLVED');
NR> ERROR 1064: You have an error in your SQL syntax near
NR> 'when,field,oldvalue,newvalue) values
NR>
'when' is a reserved word in 3.23
--
"There cannot be a crisis today. My schedule is already full."
--Henry Kissinger
> -Original Message-
> From: Noah Romer [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 02, 2001 14:38
>
> In the process of moving a database to a new server
In the process of moving a database to a new server, I decided to upgrade to
the 3.23 series MySQL, as it had been declared "stable" and has some new
features I want to investigate. However, I've had to drop back to 3.22.22, as I
started getting an "invalid SQL syntax" error on certain insert comm