#3148: Add getters and setters to model fields
-----------------------------+----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: telenieko
Status: assigned | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------+----------------------------------------------
Comment (by SmileyChris):
Replying to [comment:11 telenieko]:
> Before anything, if you look at the attached patch from TRAC it might
seem that everything is on the same function (`Field.__init__()`,
> but that's not the case, there are two functions patched here:
`Field.__init__()` and `Field.contribute_to_class()`. (See the line marked
with dots in TRAC's diff viewer).
Oops, rather big oversight on my part :P I should probably apply patches
rather than just reviewing them from trac's visual diff...
So I guess you can ignore all of points 2 and 3.
> Uhm.. really nice idea, I'll update the patch later with this change.
> Before updating, do you really thing the parameter to Field should not
be `property`?
Nah, I'm cool with it then - for example, Models have an `id` property so
the precedence has been set :)
--
Ticket URL: <http://code.djangoproject.com/ticket/3148#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
-~----------~----~----~----~------~----~------~--~---
