How many times was type_info() being called?
Tim.
On Mon, Jul 02, 2001 at 01:19:10PM -0500, Dean Kopesky wrote:
Hi!
While testing an application that generates SQL based on data extracted
from a database, I noticed that almost 80% of the runtime was being
consumed by DBI::db::quote(). A
. **
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
- Original Message -
From: Tim Bunce [EMAIL PROTECTED]
To: Dean Kopesky [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, July 03, 2001 12:46
Subject: Re: DBD::_::db::type_info() slow
It sounded like he was calling it for nearly every value he was inserting
into his SQL. A standard location for caching the type_info information
would probably also help those DBDs that are simulating placeholders.
Yes, indirectly. I am calling quote() for every value, and quote() was
Hi!
While testing an application that generates SQL based on data extracted
from a database, I noticed that almost 80% of the runtime was being
consumed by DBI::db::quote(). A significant portion of that was in
DBD::_::db::type_info(). By caching the results of type_info_all(), which
