ginal Message -
From: "Mika Tuupola" <[EMAIL PROTECTED]>
To: "Peter Beckman" <[EMAIL PROTECTED]>
Cc: "Dave Smith" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 25, 2002 11:30 AM
Subject: Re: [PHP-DB] Sessions Vs DB Access
>
On Sun, 24 Nov 2002, Peter Beckman wrote:
> Don't forget that you can use the DB to store PHP Sessions as well, which
> is faster than storing the sessions in /tmp on the file system. If you
> have well written SQL, you can have 5-30 queries per page, most of which
> should return the data in und
Don't forget that you can use the DB to store PHP Sessions as well, which
is faster than storing the sessions in /tmp on the file system. If you
have well written SQL, you can have 5-30 queries per page, most of which
should return the data in under 1/100 of a second.
I was running a site doing 1
Chris,
I'm assuming you're running this thing on *nix.
Session variables are stored on the file system. PHP writes them out to
/tmp, where it subsequently reads them upon request. The question is:
How good at caching is your DB? If it can cache common select queries,
then you are probably bett
Hi there everyone,
I have a system I am programming, and each page needs to get various config
elements from a DB, of course this means lots of DB access for each page.
What I was wondering is, after the user has logged in successfully it
currently stores their email, name, address and a few other
