17

What's the best field type to use to store MAC addresses in a MySQL database? Also, should it be stored with a certain separator (colon or dash) or should it be stored without a separator?

Nick
  • 171
  • 1
  • 1
  • 3

3 Answers3

32

use bigint unsigned (8 bytes) then you can:

select hex(mac_addr) from log;

and

insert into log (mac_addr) values (x'000CF15698AD');
Jon Black
  • 16,223
  • 5
  • 43
  • 42
  • so you can also put Infiniband GUIDs :-) – Andre Holzner Sep 17 '15 at 07:29
  • 1
    In this example, the hex() function would return : CF15698AD, which is not a mac address. When you run __select hex(mac_addr)__, the output is not always in 12 characters as you would expect. – Mathieu Châteauvert Feb 15 '19 at 15:41
  • @jon black MAC addresses, for Ethernet devices anyway. are six bytes in length. Should unsigned INT(6) work? Is unsigned BIGINT(8) being suggested instead of unsigned INT(6) solely to support infiniband GUIDs? – Billy left SE for Codidact Dec 15 '20 at 04:39
2

Take a look here. Generally, CHAR(12) is good but details depend on your needs. Or just use PostgreSQL, which has a built-in macaddr type.

Christian
  • 1,499
  • 2
  • 12
  • 28
1

Given that MySQL does not support user defined extensions, nor does it seem to support arbitrary extensions or plugins (just for storage engines), your best bet is to store it as a CHAR(17) as an ASCII string in standard notation (e.g., with colon separators), or a small BLOB and store the bytes directly. However, the string notation is going to be more friendly for most applications.

You may want to pair it with a trigger that validates that it is a MAC address, since that is really the only way to enforce data validity without support for custom types.

Michael Trausch
  • 3,187
  • 1
  • 21
  • 29