No, the Win32::ODBC does NOT support to prpepare an SQL statement to be executed later.
You can't ship around that by simply using Win32::DBIODBC, cause that's only an implementation of the above, to make it accessible through DBI.
So your solution might be to use the Perl DBI with the DBD::ODBC wich supports what you need. Then you could do :
{call procedure_name}
but note that the parenthesis is important. For the use of DBD::ODBC please refer to the DBI and specific DBD man pages and you also might want to think about reading "Programming the Perl DBI" from ORA, where you can find the above in more detail :-)
Have a nice day
All decision is left to your taste | [reply] |
check out two things
-- I'm a solipsist, and so is everyone else. (think about it)
| [reply] |
Check to see if your dbengine supports user-defined/ pre-defined functionality. MySQL has limited support for engine-side functions. Then, you should be able to use any SQL line to indicate which functions you wish to execute on which data sets. This solution is best if you're really dealing with a function that's used alot. Keep the function in the engine rather than in a Perl sub. (Plus, it'll make other perl scripts for the engine easier to write and you won't have to worry about strange SQL arrangements in your scripts.) | [reply] |