comment on

The best fix would be to name the columns something sensible. There is a dirty hack that might get you by, though.

I know some DBDs allow one to use placeholders for column names and fill those in at the time of the execution. I asked about DBD::ODBC in the ChatterBox and kennethk checked on that possibility. He says it works through DBD::ODBC for Access and he confirmed the trick works through DBD::Oracle, too.

This defeats part of the purpose of using a prepare. The execution engine for the DB won't be able to plan the queries for the most efficient execution this way. It might allow you to use column names that have to be escaped, though.

I'd like to thank kennethk for testing the idea when I asked if it would work. He didn't feel like creating a new table with question marks in the column names just to test, but he already went above and beyond to answer the question. It's worth a shot trying it with your column names if you can't get them renamed since he confirmed the trick in general.

My preference would still be to get the columns renamed.

In reply to Re: Perl DBI + Access bind issues by mr_mischief
in thread Perl DBI + Access bind issues by KurtSchwind

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks