#11403: Django Models - Default and Choices made to Table Schema
---------------------------------------------------+------------------------
Reporter: seanmccully | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords: Models
Default Choices
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
There is a larger issue here that needs to be addressed - to what extent
should the ORM hide the discrepancies between databases? This is part of a
family of issues that we need to look at - e.g., support for ON DELETE
CASCADE/RESTRICT has similar issues.
--
Ticket URL: <http://code.djangoproject.com/ticket/11403#comment:1>
Django <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.
