Re: Performance of large queries

[prev] [thread] [next] [Date index for 2004/07/15]

On Thu, Jul 15, 2004 at 10:27:05AM +0100, colm-cdbi@xxxxxxxxx.xx.xx wrote:
> AIUI the issue is not that you are getting objects back but that
> search() is internally implemented to only get ids and then each id has
> to go back to the database to do a seperate retrieve() for the
> 'Essential columns'.  It may very well be that this is no longer true, this
> is just what it seemed to do last time I looked.  I've often
> wondered if there was a way I was unaware of to (as an option) inject all the 'Essential'
> data directly into the objects or if there was any big reason this would
> be bad - can anyone shed any light on this?

If this is true it's a bug.

search() calls sql_Retrieve(), which is implemented as:

	__PACKAGE__->set_sql(Retrieve => <<'');
	SELECT __ESSENTIAL__
	FROM   __TABLE__
	WHERE  %s

The 'only fetching IDs' should only happen, therefore, if Essential ==
Primary. Making your Essential group bigger (e.g. to All) should speed
things up if you're going to need all the data anyway. 

Tony