> A very similar question was asked recently on this list. You might like
> to consider caching whatever you create from those result sets rather
> than the result sets themselves, but APC [1] is worth looking at as I
> believe it can cache (some?) PHP vars without serialisation, using
> apc_st
; Thanks
>
> T
>
> -Original Message-
> From: Jasper Bryant-Greene [mailto:[EMAIL PROTECTED]
> Sent: 28 September 2005 11:41 AM
> To: php-general@lists.php.net
> Subject: Re: [PHP] serializing result sets or what?
>
> Thomas wrote:
> > Q: What would be
scripts)?
Thanks
T
-Original Message-
From: Jasper Bryant-Greene [mailto:[EMAIL PROTECTED]
Sent: 28 September 2005 11:41 AM
To: php-general@lists.php.net
Subject: Re: [PHP] serializing result sets or what?
Thomas wrote:
> Q: What would be the best way to save db calls for large res
Thomas wrote:
Q: What would be the best way to save db calls for large result sets?
I thought about serializing the data and then caching it (with Cache_Lite -
maybe there will be a future inclusion of such a caching scheme into the php
core or pecl?). I was not sure about performance though (n
Hi,
Having spent a little time on Google (and reading unrelated articles ...) I
would like post my question here again (as advice on the list is always very
valuable indeed!):
Q: What would be the best way to save db calls for large result sets?
I thought about serializing the data and then c
Hi,
Having spent a little time on Google (and reading unrelated articles ...) I
would like post my question here again (as advice on the list is always very
valuable indeed!):
Q: What would be the best way to save db calls for large result sets?
I thought about serializing the data and then c
6 matches
Mail list logo
