Re: Support for ON DELETE and ON UPDATE in foreign keys

[Sander Steffann]

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


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: On aggregates

[Sander Steffann]

Hi,

> DISTINCT and GROUP BY are both annotating the results. Taking many
> rows, and turning them into a single row based on a key. DISTINCT would
> be the same as GROUP BY every, field, in, the, select.

Mathematically true, but I think having two separate concepts makes the code 
easier to read. And they also map to two different SQL syntaxes, which might 
have different optimalisation consequences.

- Sander


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---