On 19 Nov 2005, at 04:07, Curt Zirzow wrote:
If you are using mysql i would use the SQL_CACHE flag, it will
eliminate the need for you to manage the cache.
You don't necessarily need to us the SQL_CACHE flag in queries - you
can just turn on the query cache globally using query_cache_type=1
Marcus Bointon wrote:
On 19 Nov 2005, at 04:07, Curt Zirzow wrote:
If you are using mysql i would use the SQL_CACHE flag, it will
eliminate the need for you to manage the cache.
You don't necessarily need to us the SQL_CACHE flag in queries - you
can just turn on the query cache globally
On 21 Nov 2005, at 10:54, Jochem Maas wrote:
having said that I don't use __autoload() - I did but it was just a
PITA -
I thought it was a good idea for a while... One major irritation with
it is that with standard error reporting you can't tell where a
missing class can't be found from
I have started making use of the APC extension to cache
opcodes, etc now I'm also trying to cache the output of some
sql queries and I want to use a hash of the query as key to
store/fetch the value e.g:
apc_fetch(md5($qry))
does anyone know of a good reason (including performance
Jared Williams wrote:
I have started making use of the APC extension to cache
opcodes, etc now I'm also trying to cache the output of some
sql queries and I want to use a hash of the query as key to
store/fetch the value e.g:
apc_fetch(md5($qry))
does anyone know of a good reason (including
On Wed, Nov 16, 2005 at 04:32:29PM +0100, Jochem Maas wrote:
I have started making use of the APC extension to cache opcodes, etc
now I'm also trying to cache the output of some sql queries and I want to
use a hash of the query as key to store/fetch the value e.g:
apc_fetch(md5($qry))
If
6 matches
Mail list logo
