Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unless you're building a really resource intensive app this is probably premature optimisation. I'd just go with whatever approach is easiest, and optimise the code later if performance proves to be a problem.</p> <p>Aside from that, there's probably not an absolute correct answer to this. There's several factors you need to weigh up:</p> <ul> <li>The time it takes to (re)construct a scene.</li> <li>The amount of memory that'd be used by inactive scenes</li> <li>How often scenes are going to be used</li> <li>How many scenes there are in total</li> </ul> <p>If constructing a scene is quick enough that a user won't notice, and doesn't involve downloading or loading extra resources then it would probably be fine to just re-render views every time. However if rendering takes a noticeable period then maybe you should think about keeping views around. Likewise, I'd definitely keep a cache of resources that might be re-used.</p> <p>On the other hand, I'd guess your views are going to be using really small amounts of memory (particularly compared to the gigs of RAM most machines &amp; phones have these days) so keeping them in memory probably isn't going to be much of an issue (unless you think you'll end up with thousands of them still in memory - really depends how many views you think the user will interact with in a single session)</p> <p>If you're really concerned about using too much memory, then you could always just cache some of the views rather than all of them - either by how likely to be re-used they are, or some sort of 'most recent views' scheme where the most recent 20 (or whatever) views are stored in memory, and the rest are constructed when they're needed. However this is a bit more complicated, and quite possibly overkill.</p>
    singulars
    1. This table or related slice is empty.
    1. POReusing Backbone Views
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USobmarg
    1. USobmarg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POReusing Backbone Views
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your insight.
      singulars
      1. PO
      1. USadampetrie
    2. CORecreating templates is easy; the code is simple and so there's little chance your code will break. But don't worry about memory for you models. Images, video and the DOM will spike memory more than anything. If you test it and it's not fast enough then you'll want to update the DOM instead of recreating a template. I've been working on PrefView for backbone (https://github.com/puppybits/BackboneJS-PerfView) it has a simple interface to reuse templates if you need more performance.
      singulars
      1. PO
      1. USpuppybits
 

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