At first glance, I'd guess it's because the PK for ringo and beatles
haven't been updated in the instances you have.
On 22 November 2013 16:31, Adam Smith wrote:
> As I was learning the Django Docs (
> https://docs.djangoproject.com/en/1.6/topics/db/models/#extra-fields-on-many-to-many-relation
As I was learning the Django Docs (
https://docs.djangoproject.com/en/1.6/topics/db/models/#extra-fields-on-many-to-many-relationships),
I found the following code not working. Is it a bug? At least the result is
unexpected.
ringo = Person(name="Ringo")
beatles = Group(name="Beatles")
m1 = Memb
I found a very simple solution using Grunt and a browser extension:
https://github.com/sinnwerkstatt/sinnwerkstatt-web/blob/master/Django-livereload.md
http://stackoverflow.com/a/20135843/2510374
Nikolay
On Monday, November 18, 2013 11:12:26 AM UTC+1, Elyézer Rezende wrote:
>
> On Fri, Nov 15, 2
On Wednesday, November 20, 2013 5:17:11 PM UTC+2, Shai Berger wrote:
>
> Hi,
>
> On Saturday 16 November 2013 21:02:00 Anssi Kääriäinen wrote:
> > Any feedback for pre/post_update idea?
> >
> As Loic said, the signals sound like they can be useful in a variety of
> situations. A couple of note
It seems the db_type() method has been called as part of WhereNode
construction always (that is, first commit introducing it is QuerySet
refactor in 2008). So, the docs are wrong. If the result is expensive to
calculate, you'll need to cache it.
I created a ticket for this, see
https://code.dj