Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You'll have to overcome the old-school way of doing it :) Meteor is a lot simpler than you think. <strong>A good rule of thumb is that if you're using jQuery to manipulate any DOM elements, you're probably doing it wrong.</strong> Additionally, if you're accessing any data without using the collection API, you'd better have good reason to do so.</p> <p>In your case, you don't need to code up any manual dependencies at all. Manual dependencies are rarely needed in most Meteor applications.</p> <p>The first thing you need to do is put all your tenants inside a <code>Meteor.Collection</code>, which will make them easier to work with. </p> <pre><code>Tenants = new Meteor.Collection("tenants"); </code></pre> <p>Your <code>tenantsBlock</code> template should look something like this (modulo some different html elements):</p> <pre><code>&lt;template name="tenantsBlock"&gt; &lt;ol&gt; {{#each tenants}} &lt;li class="name {{selected}}"&gt; &lt;span&gt;Primary Tenant: {{primaryTenant}}&lt;/span&gt; &lt;span&gt;Other Tenants: {{otherTenants}}&lt;/span&gt; &lt;span&gt;Phone Number: {{phoneNumber}}&lt;/span&gt; &lt;span&gt;Email Address: {{emailAddress}}&lt;/span&gt; &lt;span&gt;Added Date: {{addedDate}}&lt;/span&gt; &lt;/li&gt; {{/each}} &lt;/ol&gt; &lt;/template&gt; </code></pre> <p>Each document in <code>Tenants</code> should look something like the following:</p> <pre><code>{ primaryTenant: "Joe Blow", otherTenants: "Mickey Mouse, Minnie Mouse", phoneNumber: "555-234-5623", emailAddress: "joe.blow@foo.com", addedDate: "2005-10-30T10:45Z" } </code></pre> <p>Then, all the code you would need is just for the selection/deselection, and you can delete everything else:</p> <pre class="lang-js prettyprint-override"><code>Template.tenantsBlock.tenants = function() { return Tenants.find(); }; Template.tenantsBlock.selected = function() { return Session.equals("selectedTenant", this._id); }; Template.tenantsBlock.events({ 'click .name': function(e) { Session.set("selectedTenant", this._id); } }); </code></pre> <p>Once again, I reiterate that you should never be doing DOM manipulations with Javascript when using Meteor. You just update your data and your templates will reactively update if everything is done correctly. Declare <strong>how</strong> you want your data to look, then change the data and watch the magic.</p>
    singulars
    1. This table or related slice is empty.
    1. POMeteor - How can I pass data between helpers and events for a template?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAndrew Mao
    1. USAndrew Mao
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMeteor - How can I pass data between helpers and events for a template?
      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. VTAcceptedByOriginator
    1. COI'm thoroughly pleased to hear you oppose manual dom manipulation. It feels like it's fighting the framework, but I didn't quite think I had any other acceptable options. That said, my use case is a lot more dynamic than I can really relay as there will be many properties each with many tenancies and all of which could be displayed on the very next page. Nonetheless, what I'm inferring is that I should probably get over my fear of global variables, use Session without prejudice, and just unset it when the template is destroyed (to be re-rendered elsewhere).
      singulars
      1. PO
      1. USDom Ramirez
    2. COI saw a talk by David Greenspan (http://www.youtube.com/watch?v=pGQ-ax5cFnk) about adding support for a "Local reactive state" Maybe I'll just have to wait for that to get off the Session object.
      singulars
      1. PO
      1. USDom Ramirez
    3. COIt was not clear to me what you were trying to do because you didn't show any of your templates. What I've done is the simplest example that I inferred from your data. I can point you to one of my projects where there is live editing of a lot of data across many fields by many users at once, which you may find helpful: https://github.com/mizzao/CrowdMapper. One thing you may need to do is to have the tenancies and their properties in different collections, which you'll get comfortable manipulating as you get more familiar with Meteor.
      singulars
      1. PO
      1. USAndrew Mao
 

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