I'm not denying that Class::DBI will be slower than using straight DBI but in most cases this doesn't matter.Hm... "most cases". What kind of "most cases" are you thinking of? Have you used Class::DBI on a heavily loaded web site, for example?
And where it does matter, you can step outside of C::D and just use DBI and SQL.Do you have any suggestions on how you would find out when it matters? Any hints on profiling a Class::DBI app?
In reply to Re^2: Best way to do caching of Class::DBI objects from a MySQL database
by doom
in thread Best way to do caching of Class::DBI objects from a MySQL database
by eXile
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |