Any opinions? Is there another approach that I should think about? Has
anyone encountered this situation before?
For most selects it isn't that hard to turn metadata
about the query into vendor SQL. The simplest fix may
be hiding the queries behind another object that takes
in generic selects an
I am using DBI 1.27 and DBD-ODBC 0.28 with Active State perl 5.6.1 on a
win2k machine to access a MicroFocus COBOL database on an AIX box via a
middleware product called U/SQLI written by a company called Transoft.
The problem I now need to solve regards transaction processing. From the
U/SQLI
[cc to dbi-dev but please reply to dbi-users or to me]
I'm making available a pre-release version of SQL::Statement with many
new features including vastly improved parens parsing (thanks Dean
Arnold), column aliases (thanks Robert Rothenberg), new built-in
functions including SOUNDER() and REGE
