Consider int based storage for other DBs about django-postgresql-netfields HOT 3 CLOSED

I'm interested in this since our production database is still MySQL and while I do intend to migrate in the long run, it's not feasible right now. However, MySQL can only store 64bit integers so you're screwed with IPv6. Also storing an IP address and a netmask in a singe field is hard. Maybe store strings like GenericIPAddressField in django 1.4 does? Then you need to make _contains and between unavailable but for my particular use case this is not important since I just need to store IP ranges and have them properly validated.

from django-postgresql-netfields.

Mhm, I was basically hoping that using some binary/blob/numeric storage + http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html would work. As all the lookups can be implemented as bit functions on binary data. But seems that all the bit functions only operate in 64 bit, so yeah, providing a subset might be the only way to go until MySQL gets their act together.

from django-postgresql-netfields.

https://bitbucket.org/onelson/django-ipyfield tries to solve some of the same problems as this package, but has fallen back to supporting everything via VARCHAR(39) for bigints across all DBs.

from django-postgresql-netfields.