in reply to DBI not letting bind varibles in if you use a varible for the statement.
I would suggest posting the actual code snippet causing the error. Also, print out your SQL statement to verify that you have the syntax correct. However, make sure you get down to the bottom of this rather than just go the second route. I build SQL statements on the fly all the time and if I was forced to use your second example, I couldn't do that.
Random thoughts: your SQL statement was all caps. Is it that was in your program also? If so, are you getting some weird problem with field names being case-sensitive (I don't think that's it as that generates and "invalid field" message or something similar). Also, are you working with multiple fields and perhaps have your commas wrong?
Cheers,
Ovid
Update: I am totally stumped as to why single quotes would work here (as opposed to double quotes). The only things I could think could cause issues would be if you were to have unusual characters in field name (such as $, \, or @) which could cause interpolation within double quotes. Both with MySQL and MS SQL Server I've had no problem using double quotes.
Oracle's fields names are not case-sensitive? I suppose that's what they call a "feature" ala MS-Speak. Hmm... I'll have to start investigating this. I just assumed they were case-sensitive... :(
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
RE: (Ovid) Re: DBI not letting bind varibles in if you use a varible for the statement.
by jptxs (Curate) on Sep 06, 2000 at 20:37 UTC | |
by merlyn (Sage) on Sep 06, 2000 at 21:50 UTC | |
by jptxs (Curate) on Sep 06, 2000 at 22:58 UTC |