I have a legacy database with a table that has many ENUM and SET fields - it seems that Django's models cannot handle these field types - or can they? I would rather not modify the table if I can get it to work as is. Is this what CommaSeparatedIntegerField is for?
Google has not been my friend since I cannot really find anything with Django MySQL ENUM and SET fields that explains one way or the other. Maybe this should be addressed on http://docs.djangoproject.com/en/dev/ref/databases/ so it could help others with this problem. TIA, Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
