Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unfortunately you can't easily discern whether or not a client has cached a page from PHP or any server environment. You can, however, advise browsers on whether or not to cache and for how long. This is accomplished by setting the Cache-Control HTTP header (and friends). See <a href="http://palizine.plynt.com/issues/2008Jul/cache-control-attributes/" rel="nofollow">this page</a>. Most folks tend to specify caching for up to a few hours in the future, so users will see stale data for no more than 2 hours. I'd recommend this, but you can also instruct browsers to effectively turn caching off altogether. Anyhow, the simplest solution in my opinion is to set these headers in your .htaccess file.</p> <p>Here's an example with a 2-hour time limit:</p> <pre><code># Cache CSS and JS files for up to 2 hours &lt;FilesMatch "\.(css|js)$"&gt; &lt;IfModule mod_headers.c&gt; # Set Max-age to 7200 seconds (2 hours), revalidate after 2 hours (ask the server if the file's changed) Header set Cache-Control "max-age=7200, must-revalidate" &lt;/IfModule&gt; FileETag MTime Size &lt;/FilesMatch&gt; </code></pre> <p>Another option is to allow caching, but force the client to ask the server if anything has changed on every request. This won't have as large of a benefit, especially on pages serving many css and js files (normally the case with Drupal) as the browser will still have to make a round-trip request to the server for each file:</p> <pre><code># Only use cache if checking with the server results in a 304 (Not Modified) &lt;FilesMatch "\.(css|js)$"&gt; &lt;IfModule mod_headers.c&gt; # Instruct the client and possibly proxies in front of the client to check for new versions every 0 seconds (always) Header set Cache-Control "max-age=0, public, must-revalidate, proxy-revalidate" # For older browsers Header set Expires "Thu, 01 Jan 1970 00:00:00 GMT" &lt;/IfModule&gt; FileETag MTime Size &lt;/FilesMatch&gt; </code></pre> <p>Finally, you can ask the browser to disable caching. I wouldn't recommend this unless you're certain that files will change very frequently, as page load times will suffer:</p> <pre><code># Disable caching &lt;FilesMatch "\.(css|js)$"&gt; &lt;IfModule mod_headers.c&gt; Header set Cache-Control "no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0" # For older browsers Header set Expires "Thu, 01 Jan 1970 00:00:00 GMT" &lt;/IfModule&gt; FileETag MTime Size &lt;/FilesMatch&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCache issue with firefox on a drupal site
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USZach Shipley
    1. USZach Shipley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCache issue with firefox on a drupal site
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis is the best answer I've ever received on stackoverflow. I'll try it first thing Monday, thanks!
      singulars
      1. PO
      1. USprashn64
    2. COJust about got this working, but I noticed I had to refresh to make the max-age show up in the header. Should I add the .htaccess file to the FilesMatch?
      singulars
      1. PO
      1. USprashn64
    3. COIf I'm understanding what you're saying correctly, that's what should happen. Your browser will cache the max-age header (and the file) and not re-check with the server until that max-age time is up. You didn't have a max-age set before, so the browser was caching indefinitely and your updates to your .htaccess would not be reflected until you cleared your cache. Which is a long way of saying: no worries, you're doing it right!
      singulars
      1. PO
      1. USZach Shipley
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload