I'm trying to write a custom field definition for a Python object that happens to be iterable. Most of the time it works, but sometimes I get an error generated in 'django/db/models/sql/where.py' in '_prepare_data' where the code tries to generate all the values in the iterable object because it's assuming that because the object is iterable it is a actually a list of objects that are part of a constraint.
I'm wondering if anyone with more intimate knowledge of Django can tell me if this is a localised assumption or if it's more general and could be amenable to patching. Incidentally, the object is to make it possible to have an IPNetwork object from the 'netaddr' package usable as a database object. The results of an iteration of this type is a list of the individual IP addresses defined by the network object. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6d2caec7-6206-4660-811a-6bf51c4684f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
