June 30th, 2000, 09:41 AM
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?
</? echo "source available on request" ?>
June 30th, 2000, 10:25 AM
Make the link to return to your index page a button, - call it 'edited' or something.
On your index pages test for <?if($edited);?> and call your db_connection from there.(the else can also call the connection) this will force a refresh wether your browser wants it or not.
June 30th, 2000, 10:34 AM
thanks, but i tried adding
header("Cache-Control: no-cache, must-revalidate");
to the page, and this seems to of taken care of it!