Opened 9 years ago

Closed 9 years ago

#25450 closed New feature (wontfix)

HostnameField (Feature request)

Reported by: Thomas Güttler Owned by: nobody
Component: Database layer (models, ORM) Version: 1.8
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Thomas Güttler)

I ask myself why is there now database field for a hostname?

GenericIPAddressField exists.

I never store IPAddesses. If I store something like this, I store hostnames.

Please add a HostnameField to store strings like "example.com"

Validation: Just check it against a regex.

Change History (2)

comment:1 by Thomas Güttler, 9 years ago

Description: modified (diff)

comment:2 by Tim Graham, 9 years ago

Resolution: → wontfix
Status: new → closed

There's an open ticket for adding a DomainNameValidator (#18119). Once that's completed, I think you could implement this as a CharField that specifies that validator. I don't think there's a compelling reason to create a new model field class, but feel free to bring it up on the DevelopersMailingList if you can expand your rationale and want to get other opinions. The difference with GenericIPAddressField is that it has a different database representation on some databases like PostgreSQL ("inet").

Note: See TracTickets for help on using tickets.
Back to Top