[Django] #25450: HostnameField (Feature request)

[Django]

#25450: HostnameField (Feature request)
----------------------------------------------+--------------------
Reporter: guettli | Owner: nobody
Type: New feature | Status: new
Component: Database layer (models, ORM) | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
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.

--
Ticket URL: <https://code.djangoproject.com/ticket/25450>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#25450: HostnameField (Feature request)
-------------------------------------+-------------------------------------

Reporter: guettli | Owner: nobody
Type: New feature | Status: new

Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0

-------------------------------------+-------------------------------------
Changes (by guettli):

* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0

Old description:

> 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.

New description:

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.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/25450#comment:1>

[Django]

#25450: HostnameField (Feature request)
-------------------------------------+-------------------------------------

Reporter: guettli | Owner: nobody
Type: New feature | Status: closed

Component: Database layer | Version: 1.8
(models, ORM) |

Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0

-------------------------------------+-------------------------------------
Changes (by timgraham):

* status: new => closed
* resolution: => wontfix

Comment:

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").

--
Ticket URL: <https://code.djangoproject.com/ticket/25450#comment:2>