Hi Patryk, While I understand your use case, I believe your proposal is lacking an argument as to why this should belong in core instead of in a third-party module. Considering it's restricted to PSQL, I find the maintenance burden hard to justify.
Cheers, André Terra On Jun 26, 2013 12:20 PM, "Patryk Ściborek" <[email protected]> wrote: > Hi! > > 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-MACADDRin > other databases it can be represented as char(17). > > If you agree to add new field type I can prepare patch against current > code. > > Kind regards, > Patryk > > -- > 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. > > > -- 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.
