On May 19, 2009, at 10:41 AM, Marcin Krol wrote:
> > Hello everyone, > > I have a table of Features. Simple enough for basic usage, but what > if I > wanted Features to provide and require other Features? Akin to > RedHat's > RPM packages that "provide" and "require" capabilities? > > E.g. I would have AntiSpam feature that requires EmailServer feature > and > provides SpamAsssassin feature. > > So I would want Feature class to contain "provides" collection that > would be a list of other Features provided, and "requires" collection > that would be a list of other Features required. > > In principle, this could be nicely done in SQLA with self-referential > many-to-many relation. But is it possible in SQLA? Or would SQLA data > structures just lock up with such circular references? > > Caveats? Special things to account for? no issues at all. the only thing that would throw it off is if a single Feature object pointed to itself. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---