In theory, I suppose you might be able to create the class that way, but I can't imagine it would be very useful. Even if you specify different db_column for each field to make the database happy, Django would probably give you some fits. When you retrieve a record from the database, Django sets attributes on the object, using the names of fields, so if you had two with the same name, one of the two would probably overwrite the other.
I haven't tried it out, but I really don't think it'd be a good idea. Why do you think you need to? -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
