"... this provides the opportunity to fully utilize this and similar kind of functionalities, in the actual implementation, to gain the best performance."
Does anyone know if Class::DBI actually does this? (Uses optimal implementation-specific functionality, for example in Oracle?)
I read perldoc Class::DBI and the explanation for retreive_all doesn't say whether it does so. One of the reasons I have avoided Class::DBI is I worry its SQL must be heavily suboptimal to facilitate operation on everything from SQLite to Oracle. I remember reading a comment on PM from someone who was monitoring Class::DBI SQL queries in real time and reported being mildly horrified (I have never been able to find the post).
In reply to Re^3: Class::DBI not intuitive
by ryantate
in thread Class::DBI not intuitive
by Jaap
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |