Hi Grant:

The answer to your question depends on a lot of details. In most cases, the
solution you have chosen is just fine. The real question you need to answer
is, "Does your solution meet your needs?" If you can answer yes to this
question, your solution is fine.

Your solution gives you a couple of advantages:
1. As you said, fewer hits against the database.
2. Faster downloads for your user. Static HTML pages download faster than a
dynamic alternative.
3. Static pages will get crawled and added to search engines; sometimes
dynamic pages won't.

Some disadvantages:
1. You have a delayed update to your Web page. If a faculty member notices a
critical error on a Web page, they must contact you or otherwise figure out
how to trigger an update.
2. There are things you can do with a dynamic page that you cannot do with a
static page.

> Here's my QUESTION! Because some of the program information is large I
don't
> want to query the data base everytime do I?

Like I said, your solution will probably work just fine, but it is probably
unnecessary. You say the program information is large, but it would have to
really REALLY large for it to make much difference. With a college of 1600
students, it does not sound like your Web site is going to have much
traffic.  Php and MySQL are pretty efficient.

My advice is to test your assumptions; does retrieving the large Web pages
from the database make much difference?

Good luck,

Matt

Matthew P Baranowski
Data Manager, Office of Educational Assessment
University of Washington


----- Original Message -----
From: Grant Cooper <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 26, 2002 10:38 PM
Subject: Data base driven web page idea - need help!


> I need help. I am building a database for a small college that wants to be
> able to update their program  information for each department through an
> web/gui program.
>
> I've decided to use, MYSQL, Apache, PHP and FreeBSD as the OS. (I built my
> web page this way)
>
> Here's my QUESTION! Because some of the program information is large I
don't
> want to query the data base everytime do I?
>
> This would take up to many resources. So I've decided to write a program
> that will take the information from the MYSQL tables and build static
pages
> every night and remove the old ones through a cron job?
>
>  How does this sound?
>
> Is this standard practice, if not what would be a better way of doing
this.
> This college has about 1600 students?
>
> Thanks in advance, I plan on doing alot of planning and really apreciate
> reading this email.
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to