>
> >> Known Facts:
> >>
> >> 1. Deleting any Topping object (for example, deleting id=1,
> >> name="Pepperoni") also removes it from foopizza.toppings. Good.
> >> 2. No m2m_changed signal is sent when 1 (above happens). BAD.
>
> ...
>
> Check this out ;)
> https://docs.djangoproject.com/en/d
On Wed, Feb 15, 2012 at 12:37 AM, Marc Aymerich wrote:
> On Tue, Feb 14, 2012 at 8:02 PM, Jeff Blaine wrote:
>> Hi all,
>>
>> I'm having trouble detecting changes that happen to a M2M field behind the
>> scenes: as a result of one of the *referenced objects being deleted*
>>
>> I'm using Django 1
On Tue, Feb 14, 2012 at 8:02 PM, Jeff Blaine wrote:
> Hi all,
>
> I'm having trouble detecting changes that happen to a M2M field behind the
> scenes: as a result of one of the *referenced objects being deleted*
>
> I'm using Django 1.3.1 with PostgreSQL 8
>
> Let's say we have the following simpl
On Feb 14, 9:02 pm, Jeff Blaine wrote:
> Hi all,
>
> I'm having trouble detecting changes that happen to a M2M field behind the
> scenes: as a result of one of the *referenced objects being deleted*
>
> I'm using Django 1.3.1 with PostgreSQL 8
>
> Let's say we have the following simple proof of co
Hi all,
I'm having trouble detecting changes that happen to a M2M field behind the
scenes: as a result of one of the *referenced objects being deleted*
I'm using Django 1.3.1 with PostgreSQL 8
Let's say we have the following simple proof of concept models:
class Topping(models.Model):
name
5 matches
Mail list logo