Re: Session storage vs. frequent DB calls

From: Rune (year)
Date: 07/30/04 

Date: Fri, 30 Jul 2004 19:05:39 +0200

Actually, and I feel slightly stupid saying this, the surveys so far have
been running on an Access database (which explains the slow-down), while the
future planned surveys will probably run on mySQL - not Access anyway.

The thing is, while I have been an advocate of the frequent DB calls
approach (mainly due to convenience and ease of implementation), my fellow
developer was suggesting the "store in sessions, save all data in DB at the
end" approach, due to the lower frequency of DB calls. - Hearing you guys
say that the DB calls overhead really is neglible (when run on a proper
database) is very nice actually. :)

Thanks for the feedback.

Rune