Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Updated answer based on need for passing in <code>user</code> object.</p> <p>The easiest way is to deal with this in your view, but it has its problems.</p> <pre><code>for widget in widget_list: widget.latest_finished_widget = widget.finished_widget_set.filter(user=request.user).latest('created') {% for widget in widget_list %} &lt;p&gt;{{ widget.name }}&lt;/p&gt; &lt;p&gt;{{ widget.latest_finished_widget }}&lt;/p&gt; {% endfor %} </code></pre> <p>While this code is easy to write, it suffers from executing a db query for every iteration.</p> <p>One quick solution is called query partitioning. Use 2 queries and python to populate the reverse relationship as efficiently as possible without going to SQL.</p> <pre><code>widgets = Widget.objects.filter(...) finished_widget_map = dict( [(x['thing__id'], x['created']) for x in Finished_Widget.objects.filter(thing__in=widgets, user=request.user).values_list('thing__id', 'created').order_by('created')]) # this ensures we only select what we need, thing__id and the created column # ordering by created will ensure only the last (latest) will appear in our dictionary for widget in widgets: widget.latest_finished_widget_created = finished_widget_map.get(widget.id, 'No Widget') {% for widget in widgets %} {{ widget.name }} {{ widget.latest_finished_widget_created }} {% endfor %} </code></pre> <p>There are always tradeoffs though. This could potentially be slow if there are many many Finished_Widgets python is pointlessly trying to populate a dict with.</p>
    singulars
    1. This table or related slice is empty.
    1. POQuerying data from a specific related object in Django template
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USYuji 'Tomita' Tomita
    1. USYuji 'Tomita' Tomita
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POQuerying data from a specific related object in Django 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. COYuji, I think you might have accidentally highlighted why I'm having so much trouble with this. Can you explain where you're getting 'finished_widget_set' from? It looks like it might be some aspect of django template syntax that I can't find the documentation on? Or are you assuming I'll be defining that elsewhere?
      singulars
      1. PO
      1. USIanWhalen
    2. CO@IanWhalen, great question! Yes, django automatically generates convenience methods for retrieving relations "backwards" http://docs.djangoproject.com/en/dev/topics/db/queries/#following-relationships-backward -- by default: fieldname_set. Still, it's inefficient as you might imagine 1 query per widget. It's more useful when you have one object and want all 100 related objects, not 100 objects each with 1 related object you'd like.
      singulars
      1. PO
      1. USYuji 'Tomita' Tomita
    3. COPS: template dot notation is strictly python based and there is no special template syntax, aside from the dot notation : ) http://docs.djangoproject.com/en/dev/ref/templates/api/#render It does python dict lookup, attr lookup, index lookup, then fails silently. So if there's a dot notation method you don't recognize, it's a python dict key, attr, or index!
      singulars
      1. PO
      1. USYuji 'Tomita' Tomita
 

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