ryuslash/site
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Highlight?

Browse source
This commit is contained in:
Tom Willemsen 2012-11-04 19:13:22 +01:00
parent 124cdee6ba
commit 7ee8c1a038
1 changed files with 12 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
posts/Silly_django_confusion.mdwn
View file

@ -8,29 +8,30 @@ page. So this is what I found:
[[!format sql """ [[!format sql """
SELECT * FROM app_table; SELECT * FROM app_table;
=> 3 rows of data
"""]] """]]
<pre class="src src-sql">SELECT * FROM app_table; [[!format py """
=&gt; 3 rows of data</pre> from app.models import Table
<pre class="src src-python"><span class="org-keyword">from</span> app.models <span class="org-keyword">import</span> Table
Table.objects.count() Table.objects.count()
=&gt; 3 => 3
Table.objects.<span class="org-builtin">all</span>() Table.objects.all()
=&gt; []</pre> => []
"""]]
This is weird. So I looked at the `django.db.connection.queries` This is weird. So I looked at the `django.db.connection.queries`
property and I realized that it was doing a join since the model property and I realized that it was doing a join since the model
subclasses another: subclasses another:
<pre class="src src-python"><span class="org-keyword">from</span> django.db <span class="org-keyword">import</span> models [[!format py """
from django.db import models
<span class="org-keyword">from</span> app.models <span class="org-keyword">import</span> SuperTable from app.models import SuperTable
<span class="org-keyword">class</span> <span class="org-type">Table</span>(SuperTable):...</pre>
class Table(SuperTable):...
"""]]
Which, of course, means that in order to get the complete `Table` Which, of course, means that in order to get the complete `Table`
instance, the related `SuperTable` instance is also required, but in instance, the related `SuperTable` instance is also required, but in