hi. I was thinking it might be a good idea to have a meta.SiteModel class to inherit from for site-specific models. (ie.. you have 5 sites with articles stored in the same table) and it would do all the hard work for you.
so instead of having something like class Article( meta.Model): site = ForeignKey( core.site) ... and then having to remember add 'sites__id__exact=SITE_ID' each time you query the table. you could do something like class Article( meta.SiteModel): ... and meta.SiteModel would - add the site field for you - automatically append sites_id_exact in ALL queries (by checking the klass in things like function_get_values_iterator) - modify the uniqueness contstraints of the other fields so that they include the site in the key. (allowing you to have the same slug value over multiple sites) why bother? for me I like the idea that I can site-enable an application with a minimum of fuss, and not having to remember to add the site_id__exact query in every view I have. Regards ian -- [EMAIL PROTECTED] -- ++61-3-9877-0909 If everything seems under control, you're not going fast enough. - Mario Andretti
