MySQL Bugs: #34037: ipv6-capable inet_aton and inet

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
Category:	Server: General	Severity:	S4 (Feature request)
Version:	any+	OS:	Any
Assigned to:	Alexander Nozdrin	Target Version:
Tags:	TCP/IP
Triage:	Triaged: D5 (Feature request)

Description:
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:
-

Since ipv6 is almost in use, how would one design a table which wants to store an ipv4 of an ipv6 ip?

ipv4 addresses can be represented in ipv6 in the style :::127.0.0.1 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.

Bug #48594  was marked as a duplicate of this one.

Bug #48595 was marked as a duplicate of this one.

There are some great third party UDFs available here for this as a workaround:
http://labs.watchmouse.com/2009/10/extending-mysql-5-with-ipv6-functions/

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?

Bug#15127 has been marked as a duplicate of this bug.