Hi Mike,
> If I can determine that there is sufficient interest that there's a
> decent chance of it being used (always assuming the implementation is
> found acceptable, of course), I'll definitely work on it.
+1
This feature would be very nice to have.
Thanks!
Sander
Russell Keith-Magee wrote:
> On Thu, Jun 19, 2008 at 11:00 PM, Michael Glassford
> <[EMAIL PROTECTED]> wrote:
>> Now for one of the reasons that I've been trying to get the Django unit
>> tests running: I'm interested in submitting a patch that adds some ON
>> DELETE and ON UPDATE support in
I've implemented some code already to de-reference (SET_NULL) on
delete, in a view which first presents a list of objects which will be
deleted and a list of objects which will be de-referenced. It might
not be the most efficient approach, but it could be a starting point.
def _clear(instance):
On Thu, Jun 19, 2008 at 11:00 PM, Michael Glassford
<[EMAIL PROTECTED]> wrote:
>
> Now for one of the reasons that I've been trying to get the Django unit
> tests running: I'm interested in submitting a patch that adds some ON
> DELETE and ON UPDATE support in Django. But first, I want to see
Marc Fargas wrote:
> El jue, 19-06-2008 a las 11:00 -0400, Michael Glassford escribió:
>> * If settings.DATABASE_HANDLES_ON_DELETE=True, the SQL that is generated
>> by manage.py contains ON DELETE clauses where on_delete= is
>> specified.
>>
>> * If settings.DATABASE_HANDLES_ON_UPDATE=True,
El jue, 19-06-2008 a las 11:00 -0400, Michael Glassford escribió:
> * If settings.DATABASE_HANDLES_ON_DELETE=True, the SQL that is generated
> by manage.py contains ON DELETE clauses where on_delete= is
> specified.
>
> * If settings.DATABASE_HANDLES_ON_UPDATE=True, the SQL that is generated
>
Now for one of the reasons that I've been trying to get the Django unit
tests running: I'm interested in submitting a patch that adds some ON
DELETE and ON UPDATE support in Django. But first, I want to see what
interest there is in such a patch. There have been a number of tickets
about this
