#10896: UrlField cannot be used with relative URLs
---------------------------------------------------+------------------------
Reporter: notanumber | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: wontfix | Keywords: url
urlfield relative
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
Suspect the solution here is to use a different field. Right now, we
require absolute URLs and you want a `RelativeURLField`, which carries a
whole bunch of bonus assumptions or requirements (e.g. relative to
''what''?) that make it not usable in all the same places that `URLField`
is.
Since subclassing fields is fairly easily, encouraged and supported, let's
not modify the existing field. Whether it's worth including the subclass
in Django itself is a conversation to be had in the future after the
subfield has existed for a while and adopted a massive userbase.
For now, though, closing as wontfix, since it appears to work as intended
and as a feature change to an existing field, things get complicated fast.
If all the problems are overcome when development is done, it's worth a
discussion on django-dev, but that is also for the future.
--
Ticket URL: <http://code.djangoproject.com/ticket/10896#comment:3>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
