#2160: Can't use value of 0 for primary key
-------------------------------------------+--------------------------------
Reporter: fgutierrez AT aureal.com.pe | Owner: adrian
Status: reopened | Component: Database
wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design
decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 1
-------------------------------------------+--------------------------------
Comment (by mtredinnick):
Whilst I completely agree with Russell's design philosophy here, reality
gets in the way in practice. Oldforms exists and there are apps in the
wild that create models using those idioms. So having pk_val being the
empty string is going to be with us for a while, even beyond 1.0. I think
we have to live with the slight ugliness. Ruling out certain valid primary
key values to save a less-than-perfect test in the code feels like we are
handicapping the wrong people.
--
Ticket URL: <http://code.djangoproject.com/ticket/2160#comment:12>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
