On Fri, Jul 28, 2006 at 03:46:20PM +0100, Martin J. Evans wrote:
On 27-Jul-2006 Tim Bunce wrote:
On Wed, Jul 26, 2006 at 10:43:34AM +0100, Martin J. Evans wrote:
On 25-Jul-2006 Tim Bunce wrote:
Use DBI::Profile to see where the time is being spent.
I got this working and could
On Wed, Jul 26, 2006 at 09:51:02AM +0100, Martin J. Evans wrote:
On 25-Jul-2006 Tim Bunce wrote:
Use DBI::Profile to see where the time is being spent.
I am looking into this.
My first attempt at setting DBI_PROFILE=2 and running my script returned with:
DBI::Profile on_destroy
On Wed, Jul 26, 2006 at 10:43:34AM +0100, Martin J. Evans wrote:
On 25-Jul-2006 Tim Bunce wrote:
Use DBI::Profile to see where the time is being spent.
I got this working and could not see anything taking longer. However, on
further investigation of my logs I have found the reason why
On 25-Jul-2006 Tim Bunce wrote:
Use DBI::Profile to see where the time is being spent.
I am looking into this.
My first attempt at setting DBI_PROFILE=2 and running my script returned with:
DBI::Profile on_destroy failed: Undefined subroutine DBI::Profile::time_in_dbi
called at
On 25-Jul-2006 Tim Bunce wrote:
Use DBI::Profile to see where the time is being spent.
I got this working and could not see anything taking longer. However, on
further investigation of my logs I have found the reason why doing a
prepare_cached on select LAST_INSERT_ID() to mysql is a BAD thing
On 26-Jul-2006 mark wrote:
I know nothing about MySQL, but I benchmarked prepare vs prepare_cached
in Oracle many moons ago, and saw no great difference, which is actually
what I expected. In theory, the main savings is avoiding the repeated
cost of the database parsing and prepping the
I know this is one of those how long is a piece of string questions but
I cannot see any difference using prepare_cached with a remote mysql or
oracle database. I have code which does inserts/updates/selects - around
20 - 30 different pieces of SQL and most of them are run between a 100
and 1000
I know nothing about MySQL, but I benchmarked prepare vs prepare_cached
in Oracle many moons ago, and saw no great difference, which is actually
what I expected. In theory, the main savings is avoiding the repeated
cost of the database parsing and prepping the statement, but Oracle
does its own
