Re: [PHP] DB calls vs Session solution

2006-03-13 Thread Grant Young
Hi Jochem. the nice thing about programming with my 'data framework' is that its very generic, flexible and interspective (generating abitrarily complex sql/html/? from objects) ... which comes with a great cost. so I have code that is really very very heavy but if you consider the (complete|di

Re: [PHP] DB calls vs Session solution

2006-03-13 Thread Jochem Maas
Curt Zirzow wrote: On Mon, Mar 13, 2006 at 03:30:18PM +0100, Jochem Maas wrote: I just realized I must be evil ;-) Arn't we all :) more so for the random switch to inline+bottom posting :-) ... Ah, see this is a bit different, and goes along the theory of a cost has to come from s

Re: [PHP] DB calls vs Session solution

2006-03-13 Thread Curt Zirzow
On Mon, Mar 13, 2006 at 03:30:18PM +0100, Jochem Maas wrote: > I just realized I must be evil ;-) Arn't we all :) > secondly I take 'the cache your db results in the session' > to an extreme - by shoving serialized ResultSet objects (with all > results in tow of course) into shared memory by way

Re: [PHP] DB calls vs Session solution

2006-03-13 Thread Jochem Maas
I just realized I must be evil ;-) firstly I'm top posting. secondly I take 'the cache your db results in the session' to an extreme - by shoving serialized ResultSet objects (with all results in tow of course) into shared memory by way of the APC extension... this is of course evil because Rasm

[PHP] Re: [SPAM] Re: [PHP] DB calls vs Session solution

2006-03-13 Thread joseph
> > > > I have got some expensive sql queries (doing lots of LEFT JOINS) that result > > in anything between 10 to 1 results. I need to do paging on those. So > > far I have used a LIMIT solution which will not do anymore because you don't > > get the whole total. i just decided to issue a cou

Re: [PHP] DB calls vs Session solution

2006-03-12 Thread Curt Zirzow
On Fri, Mar 10, 2006 at 02:10:54PM +0200, Thomas wrote: > > Hi there, > > Quick question on performance: > > I have got some expensive sql queries (doing lots of LEFT JOINS) that result > in anything between 10 to 1 results. I need to do paging on those. So > far I have used a LIMIT solution