Re: How to express a seemingly straightforward upate in the ORM?

Den 12/09/2014 kl. 20.19 skrev Benjamin Scherrey : > I should assume then that this is something that the existing Django ORM > cannot model? It's a bit hard for me to grok your initial mail, but maybe you can use the new Prefetch() class in Django 1.7 to filter your

Re: How to express a seemingly straightforward upate in the ORM?

I should assume then that this is something that the existing Django ORM cannot model? -- Ben On Mon, Sep 8, 2014 at 1:06 PM, Benjamin Scherrey wrote: > I've got an application that needs to frequently update a boolean value > (ChannelItem.channel_stocks) against a

How to express a seemingly straightforward upate in the ORM?

I've got an application that needs to frequently update a boolean value (ChannelItem.channel_stocks) against a temporary table that gets created and lives just long enough for this transaction. The table is simply a list of alpha-num skus and created like this: cursor.execute("create temporary