Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Warning: Advanced Tricks ahead!</strong></p> <p><em>Render them all</em>. Hide the ones that you don't need using CSS/Javascript, which can be trivially initialized in any number of ways. (Javascript can read the URL used, query parameters, something in a cookie, etc etc.) This has the advantage of potentially playing much better with your cache (why cache three views and then have to expire them all simultaneously when you can cache one?), and can be used to present a better user experience. </p> <p><strong>For example</strong>, let's pretend you have a common tab bar interface with sub navigation. If you render the content of all three tabs (i.e. its written in the HTML) and hide two of them, switching between two tabs is trivial Javascript and <strong>doesn't even hit your server</strong>. Big win! No latency for the user. No server load for you.</p> <p>Want <strong>another big win</strong>? You can use a variation on this technique to cheat on pages which might but 99% common across users but still contain user state. For example, you might have a front page of a site which is relatively common across all users but say "Hiya Bob" when they're logged in. Put the non-common part ("Hiya, Bob") in a cookie. Have that part of the page be read in via Javascript reading the cookie. <strong>Cache the entire page for <em>all users regardless of login status</em> in page caching.</strong> This is literally capable of slicing 70% of the accesses off from the entire Rails stack on some sites.</p> <p>Who cares if Rails can scale or not when your site is really Nginx serving static assets with new HTML pages occasionally getting delivered by some Ruby running on every thousandth access or so ;)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I implement Section-specific navigation in Ruby on Rails?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPatrick McKenzie
    1. USPatrick McKenzie
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COUpvotes for originallity of thought. :-)
      singulars
      1. PO
      1. USmaurycy
    2. CONote that this answer *will* fail for some users if you don't first test (or assume) JavaScript or Cookies, respectively. A better answer would be to use JavaScript with partial HTML or Varnish+ESI instead.
      singulars
      1. PO
      1. USLouis St-Amour
 

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