Re: Bind param error

In your prepare statement for $sth1 you have

h.net_due_date as NET_DUE_DATE, #Added for Revision 1.6
h.status as STATUS #Added for Revision 1.6
[download]

I know a lot more Perl than SQL but I doubt those are legal SQL comments.

Comment on Re: Bind param error Download Code

Replies are listed 'Best First'.
Re^2: Bind param error by stevieb (Canon) on Jun 30, 2010 at 13:07 UTC
fwiw, those are legit SQL commands (at least in MySQL): `mysql> select username as client_name from clients limit 1; +-------------+ \| client_name \| +-------------+ \| stevieb \| +-------------+` [download] Steve	[reply] [d/l]
Re^3: Bind param error by rowdog (Curate) on Jun 30, 2010 at 21:06 UTC
Really? SQLite disagrees... `sqlite> select count() from show; # illegal comment; 27 Error: unrecognized token: "#"` [download] I guess I wasn't clear enough: Perl comments aren't valid SQL*.	[reply] [d/l]
Re^2: Bind param error by doug145 (Initiate) on Jun 30, 2010 at 18:58 UTC
Rowdog, I thought this was PERL, not SQL. Anyway, using 'as ' with aliases has worked fine in the current version of the code.	[reply]
Re^3: Bind param error by rowdog (Curate) on Jun 30, 2010 at 21:08 UTC
I wasn't questioning the commands, I was questioning the use of Perl comments in SQL.	[reply]