ansaurus

Question

MySQL rejecting parameter

Answer 1

A:

Not sure if that will work. I would change to either

VALUES (?, ?)

OR

VALUES (:COURSEID, :COURSENAME)

2009-09-22 00:53:15

:courseid is Oracle syntax, dunno for any others

OMG Ponies 2009-09-22 01:08:40

Answer 2

+1 A:

MySQL does not support named parameter placeholders. You can use only positional parameter placeholders. That is, a placeholder is just a ? symbol.

This conforms to the ANSI SQL behavior, by the way. RDBMS like Oracle support named parameters as an extension to the standard.

Bill Karwin 2009-09-22 00:55:55

Bill, I believe you've identified the problem. In the past I had used named parameters with MySQL, but I had only done so with the MySQL driver for .NET. In this case, I'm using the ODBC driver and I have a feeling it's not handling the named parameters quite the same. Thanks for the heads up thought, I didn't know named parameters weren't officially part of SQL.

T. Stone 2009-09-22 01:29:17

Right, if the .NET driver supports named parameters, it must be rewriting the query string before it sends it to the MySQL server. PHP's PDO library does something similar, so you can use named parameters with any back-end, even if it doesn't support named parameters. But it's hard to get that kind of query-rewriting right, for instance a string literal could contain characters that look like a parameter placeholder, so the query parsing in the driver has to be clever enough to tell the difference.

Bill Karwin 2009-09-22 01:35:19

ansaurus

tags:

views:

answers:

MySQL rejecting parameter

related questions