| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Jerry Schwartz | Date: | May 14 2009 2:06pm |
| Subject: | RE: MAC address as primary key - BIGINT or CHAR(12) | ||
| View as plain text | |||
You might even want to plan for longer MAC addresses. I don't follow developments in that area, but they had to go from IP4 to IP6 and they might have to introduce longer MAC addresses. It isn't hard to change a MySQL field definition, but your applications would be more of a problem. >-----Original Message----- >From: Ilia KATZ [mailto:ikatz@stripped] >Sent: Thursday, May 14, 2009 9:26 AM >To: mysql@stripped >Subject: MAC address as primary key - BIGINT or CHAR(12) > >Hi. >Currently I have a table: >1. MAC address defined as BIGINT >2. MAC address set as primary key > >Should I consider changing it to CHAR(12)? > >Replies will be appreciated. >Ilia > >
| Thread | ||
|---|---|---|
| • MAC address as primary key - BIGINT or CHAR(12) | Ilia KATZ | 14 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | Fish Kungfu | 14 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | kabel | 14 May |
| • RE: MAC address as primary key - BIGINT or CHAR(12) | Ilia KATZ | 14 May |
| • RE: MAC address as primary key - BIGINT or CHAR(12) | Jerry Schwartz | 14 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | Thomas Spahni | 14 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | Jim Lyons | 14 May |
| • RE: MAC address as primary key - BIGINT or CHAR(12) | Daevid Vincent | 14 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | Pete Wilson | 14 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | Jim Lyons | 14 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | Pete Wilson | 14 May |
| • RE: MAC address as primary key - BIGINT or CHAR(12) | Gavin Towey | 15 May |
| • Re: MAC address as primary key - BIGINT or CHAR(12) | Gavin Towey | 15 May |
