Hi, I hit this bug 10 months ago when I first started using Django and it still hasn't been addressed. As per my comments in the ticket I feel that the use of the inet type in the postgresql backend is a special case that is the root of the issue. Using a char(15) like every other backend would fix the issue and remove this special case. This will definitely cause backwards compatibility issues though.
opinions? regards matthew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
