Databases
StackOverflow2013
Postsdbo
POReverse foreign key to django-fts searchable model in template
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReverse foreign key to django-fts searchable model in template
    primarykey
    data
    text
    <p>I have a pair of Django models with a foreign key, one of which is searchable with django-fts, say:</p> <pre><code>class Foo(models.Model): ... class Bar(fts.SearchableModel): foo = models.ForeignKey(Foo) </code></pre> <p>When I have an instance of Foo, in view I can insert <code>print foo.bar_set.all()</code> and I see an array of results. However if I try to use it in a view, in any of following ways:</p> <pre><code>{{foo.bar_set|pprint}} {{foo.bar_set.all|ppring}} {{foo.bar_set.count}} {{foo.bar_set.all|length}} {% for bar in foo.bar_set.all %} {{bar}} {% endfor %} </code></pre> <p>and literally <em>any</em> construct that I can think of behaves as if <code>foo</code> instance had no <code>bar_set</code> attribute.</p> <p>Edit: I am sure that I have a <code>Foo</code> instance in the template, I tested following to work as expected:</p> <pre><code>{{foo|pprint}} {{foo.id}} (and any other simple attributes of Foo) </code></pre> <p>I am sure there are related Bar objects, as I check that from view (<code>print foo.bar_set.all()</code>). And if the QuerySet was empty, <code>{{foo.bar_set.all|pprint}}</code> would yield <code>[]</code>, not <code>''</code> (which it does on <code>{{foo.bar_set.all|pprint}}</code>, <code>{{foo.bar_set|pprint}}</code>, and any <code>{{foo.nonexistent_attribute|pprint}}</code>).</p> <p>This behaviour started when I moved development from SQLite database to PostgreSQL, with psycopg2 driver, to use django-fts full text search.</p> <p>I could not find any other answer, because googling this is very hard: "reverse relationship" or "reverse foreign key" is all littered with unrelated <code>django.core.urlresolvers.reverse</code> references, and I have no idea how to name "*_set" thing to Google. A hint on how to google this one would be helpful as well.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMaciej Pasternacki
    1. USMaciej Pasternacki
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POReverse foreign key to django-fts searchable model in template
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POReverse foreign key to django-fts searchable model in template
      1. USAlbertoPL
      1. VTFavorite
    3. VO
      singulars
      1. POReverse foreign key to django-fts searchable model in template
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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