On Sun, 2008-07-20 at 10:05 -0400, Cole Tuininga wrote: > On Sat, Jul 19, 2008 at 11:50 PM, Julien Phalip <[EMAIL PROTECTED]> wrote: > > > > 'set' is a Python standard object [1], since version 2.4. In version > > 2.3 you need to import the 'Set' package first. > > So, if you care about backward compatibility in Python, the most > > secure way to import it is: > > Oops - sorry, I wasn't very clear in my original request. I'm looking > for a set type in the Django model hierarchy. Does this make more > sense?
A set is just an unordered collection of objects. In other words, it's the rows in a database table, so it's instances of a Django model. Thus, if you want to model a set, you can use a many-to-one relation (ForeignKey) or a many-to-many relation. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
