Opened 11 years ago
Closed 11 years ago
#20661 closed New feature (duplicate)
MAC address field
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | mac address |
| Cc: | patryk@… | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi!
I would like to ask you to reconsider addition of field representing MAC address. There was similar ticket created 7 years ago: 2239 and it was closed with wontfix.
I use Django in many projects and a lot of them are related to IP networks. In many situations I need to deal with mac addresses (Ethernet addresses in wired networks, wireless radio cards addresses, BSSIDs, radio cards in APs, Bluetooth addresses, etc). PostgreSQL provides native support for macaddr data type: http://www.postgresql.org/docs/9.1/static/datatype-net-types.html#DATATYPE-MACADDR in other databases it can be represented as char(17).
If you agree to add new field type I can prepare proper patches against current code.
Note:
See TracTickets
for help on using tickets.
Please don't open duplicate tickets asking for reconsideration. The proper forum for that would be the django-developers mailing list.