Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>"The problem is that we have one JS file"</p> </blockquote> <p>I'm not sure how you can avoid it as long as you are including the same (merged) JS file for all pages. You could use some server-side logic to merge different pieces to go with different pages, but then you presumably lose the benefits of client-side caching of the JS, so...</p> <p>Projects I've worked on have (typically) used multiple JS files, a couple being common to every page, and the others being included or not as appropriate - some JS files included by only one page. This means that pretty much every page includes the common library functions whether they use them or not, but the common JS file gets cached so it doesn't really matter. Page-specific code really is page-specific.</p> <p>I can't tell from your question whether you are aware of it, but you can have multiple document ready handlers (I believe jQuery executes them in the order they were bound?). So if you do split the JS up each JS file can include its own document ready. Of course that approach has its own overhead, but I think it's better than putting everything in the same file.</p>
    singulars
    1. This table or related slice is empty.
    1. POmanaging document.ready event(s) on a large-scale website
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USnnnnnn
    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. This table or related slice is empty.
    1. COfrom a page load perspective it definitely makes sense to take the hit of downloading all of the JS up front and cache client-side, so i think a merged file is fine. But if you are doing lots of stuff in the document ready handler, it doesn't make sense to have lots of code *execute* (downloading is a one-time hit, but executing needless code is incurring a cost for every page load). I am aware of multiple ready handlers, but i don't think it really solves the issue and may incur it's own performance problems (presumably firing many events is more costly than firing one larger event)
      singulars
      1. PO
      1. USWickyNilliams
    2. COYeah, I only suggest multiple ready handlers in the scenario of multiple JS files. That way the browser is still caching the various JS files but any given page only loads the ones it needs and only executes the code it needs. I'm assuming firing many events that do only what you need is better than firing one larger event that (according to your question) may be 90% irrelevant.
      singulars
      1. PO
      1. USnnnnnn
    3. COyou make a valid point, but the main factor in page load is number of HTTP requests, and i wish to abide by this rule. I've started thinking of an approach where i can declaratively add classes to the body (server side). These would describe the type of page (to keep things semantic), using JS i could then look these up, and use them as keys to access specific pieces of functionality on some object. This extra logic and lookups will incur some cost, but should provide gains by focusing the amount of code executed per page. i'd need to benchmark. A rough prototype: http://jsfiddle.net/v5QZn/
      singulars
      1. PO
      1. USWickyNilliams
 

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