Bug #34037 ipv6-capable inet_aton and inet_ntoa functions needed
Submitted: 24 Jan 2008 15:13 Modified: 3 Feb 2011 16:09
Reporter: Domas Mituzas Email Updates:
Status: In progress Impact on me:
Category:MySQL Server: General Severity:S4 (Feature request)
Version:any+ OS:Any
Assigned to: Assigned Account
Tags: TCP/IP
Triage: Triaged: D5 (Feature request)

[24 Jan 2008 15:13] Domas Mituzas
MySQL doesn't have functions to convert between ipv6 addresses and numeric forms. 
Adding such functionality would be helpful in ipv6-enabled applications.  

How to repeat:

Suggested fix:
[29 Jan 2008 23:39] Jeff Peff
Since ipv6 is almost in use, how would one design a table which wants to store an ipv4 of an ipv6 ip?
[26 Mar 2008 17:09] Marcus Bointon
ipv4 addresses can be represented in ipv6 in the style ::: It doesn't really matter anyway - a 128-bit unsigned integer field can store a value that represents either ipv4 or v6. All we need is for iten_aton to understand ipv6 notation.
[6 Nov 2009 18:59] Valerii Kravchuk
Bug #48594  was marked as a duplicate of this one.
[6 Nov 2009 19:03] Valerii Kravchuk
Bug #48595 was marked as a duplicate of this one.
[23 Sep 2010 1:24] Trent Lloyd
There are some great third party UDFs available here for this as a workaround:
[1 Mar 2011 13:30] Rolf Martin-Hoster
Any movement on this. Its been 3 years and this year the last ipv4 space is going to be allocated. I would consider that to make it something of a priority?
[8 Apr 2011 8:34] Alexander Nozdrin
Bug#15127 has been marked as a duplicate of this bug.
[2 Jan 2014 16:12] Simon Mudd
Since you've marked bug#15127 as a duplicate I'll add the comments here but related to STORAGE of the IPv6 types:

I also think it would be good to have an IPv6 data type as a native type in the database.
- it makes it clear what the data is supposed to be
- Viewing, selecting or otherwise manipulating this type of type from the mysql command line is much harder if you don't provide this support, as you'd probably have to use a binary(16) and that in the mysql client can generate weird escape characters which mess up formatting and is thus ugly
- IPv6 support is now partly added to MySQL so this adding this data type seen like a natural thing to do

So +1 from me.
[2 Jan 2014 16:14] Simon Mudd
and related to providing support for:
- uuid (bug#68859)
- a 128-bit (signed or unsigned) integer (also sensible now we use much larger values)