On 30/11/11 07:13, Anssi Kääriäinen wrote:
> The reason for doing the deprecation now is that it would be nice that
> this behavior is already removed when multicolumn primary keys are
> introduced into Django.
>
> There is a ticket related to this: #2259.
Here is another that could be helped by this change, depending on
implementation - #14615
The decisions on that ticket basically boils down to the question of how
we detect a new object (which is waiting for PK from the DB). The
current solution of comparing with None (used in various places) fails
for nullable primary keys.
Luke
--
Noise proves nothing. Often a hen who has merely laid an egg
cackles as if she laid an asteroid.
-- Mark Twain
Luke Plant || http://lukeplant.me.uk/
--
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
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
