in reply to SQL/DBI
When preparing SQL statements to send to the server, DBI circumvents the problem of different SQL syntaxes across all the different SQL servers (Oracle, Sybase, MySQL etc) by simply taking the statement as a raw string and letting the SQL server tell you whether the syntax is valid or not.
When you &DBI::connect, give it RaiseError=>1 in the \%attr slot. Testing should then catch unimplemented SQL.
DBI is the cross-driver interface to SQL. stick to vanilla DBI.pm and most things will work.
Your example suggests that your application is pretty tightly bound to some data structures you haven't explained.
After Compline,
Zaxo
|
|---|