refreshing index page of MySQL fed web application

Anon

i can't seem to figure this one out. i created a web application that allows us to keep up a dynamic schedule on our intranet. i've got everything worked out except one detail. When ever i edit / add items to the schedule, and perform the SQL Query, then click the link to return to the main index page - i have to hit refresh on my browser to see the new / changed data!

What am i doing wrong? i'm freeing up the resultset(s) after i pull the data in. and even closing the current MySQL connecttion (to try to force a new connection when the page is revisited) - i even added pragma-nocahce and expiration meta tags to the document just to be safe!

Has anyone else ran into this problem?

-zenlab™

</? echo "source available on request" ?>

Anon

Does your query happen on the index page, If so make sure that your code for updating/editing records sits above your query for displaying the data on the page.

Anon

thanks for the reply. Actually, all my queries happen on different pages. for ease of coding. there's just something about recursive coding that doesn't sit well with me, at least not yet <G>.

the application is broken up like this.

index.php
- queries the database and loops out the mysql_fetch_array to populate the html table with the appropriate data.

edit.php
- queries the database with a "Select * FROM $db WHERE ID = $ID"
$id and $db are passed over thru the querystring...

update.php
- sends the "UPDATE ..." query and produces an "update complete" notice and a link back to the index.

and that's about it.

-zenlab™

Anon

The only thing I can say from my own experience, is that if you just run all of those relatively basic functions on one page you could line it up like this:

if ($update) {
run your update query here
}
if ($edit) {
run your edit query here
}
if (!$edit) {
run your display select query here
}

In the meat of your page you would just need to set up sections for each function:

Not only would this make your code sit in one place, but it would force the script to query the db for your records after it updates the db so you would always be getting the freshest data. I think your problem lies with your browser and caching issues, those meta tag no-cache features have never worked right for me.

Anon

thanks that's good advice... but i was able to clear it up by sending:

header("Pragma: no-cache");
header("Cache-Control: no-cache, must-revalidate");

:before the queries

thanks again!