Depends on the database and the info, I would suspect.
My bias in coding database apps for websites is having the webserver / webservers cache info it fetches / they fetch from the DB as much as possible. This makes the most sense when you're going to have several webservers interacting with a single database (because in that situation, the database is a bottleneck). If you've got something very simple and a decent DBMS, as long as there's no overhead for connecting to the database server process (i.e. if you have what are called 'persistent connections', and you will have to run your scripts under mod_perl for that), you're probably better off, speed-wise, going to the database because it will optimize the lookups for you.
HTH
perl -e 'print "How sweet does a rose smell? "; chomp ($n = <STDIN>); +$rose = "smells sweet to degree $n"; *other_name = *rose; print "$oth +er_name\n"'
In reply to Re: faster access times
by arturo
in thread faster access times
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |