Hi Patryk, On 06/26/2013 09:13 AM, Patryk Ściborek wrote: > I would like to ask you to reconsider addition of field representing MAC > address. There was similar ticket created 7 years ago: > https://code.djangoproject.com/ticket/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 addresses in access points, 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).
Do you have any new information to justify why the existing resolution of #2239 should be reconsidered? I think the existing resolution is correct. This seems like a perfect case for a third-party field class. I don't think the need to represent MAC addresses in the database is common enough in web development to warrant inclusion in Django core. Carl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
