Michael Dykman wrote:
> One problem you might be having is the column named 'call'.. It's a
> keyword, so perhaps you might get away with backticking it?ie.
> `call`
>
> Also, you shouldn't need that final semi-colon inside your statement
> string.. I have had preparedstatement interfaces gi
Grant Peel wrote:
> Hi all,
>
> I recently migrated a script called perldesk from mysql 4 to mysql 5.
>
> When I envoke the script from the web, I am now getting an error. I suspect
> its a version syntax thing.
>
> Here is what I see:
>
> Couldn't execute statement: You have an error in your
- Original Message -
From: "Grant Peel"
To: "Michael Dykman"
Cc:
Sent: Sunday, July 11, 2010 9:25 PM
Subject: Re: Mysql 4 to 5
- Original Message -
From: "Michael Dykman"
To: "Grant Peel"
Cc:
Sent: Sunday, July 11, 2010 9:20 PM
- Original Message -
From: "Michael Dykman"
To: "Grant Peel"
Cc:
Sent: Sunday, July 11, 2010 9:20 PM
Subject: Re: Mysql 4 to 5
One problem you might be having is the column named 'call'.. It's a
keyword, so perhaps you might get away with backt
One problem you might be having is the column named 'call'.. It's a
keyword, so perhaps you might get away with backticking it?ie.
`call`
Also, you shouldn't need that final semi-colon inside your statement
string.. I have had preparedstatement interfaces give me grief about
that.
As I reca
Hi all,
I recently migrated a script called perldesk from mysql 4 to mysql 5.
When I envoke the script from the web, I am now getting an error. I suspect its
a version syntax thing.
Here is what I see:
Couldn't execute statement: You have an error in your SQL syntax; check the
manual that co
