Hi Mart, I'm the per-obect-perm developher.
Depends on what magic you are looking for it to do. The row_level_permissions option in the meta class does two things that can be rewritten in a way that doesn't need to involve the db.options (meta class). The first thing the option does is create a generic relationship between the object and row level permisisons, it could have been done manually for each object by using the relation: row_level_permissions = models.GenericRelation(RowLevelPermission, object_id_field="model_id", content_model_field="model_ct") The second thing the option does is check if row level permissions are enabled and does various things with that info. I could have handeled this by checking if the relationship row_level_permissions exists on the object. Hopefully that answers some of your questions. What exactly are you looking to do? I might be able to help, or give some suggestions. As an aside, there have been a few ideas floating around for an application repository and packaging method. For that, I think it would be great if there was a way to have a method of extending the options(meta) model to include some custom options for an application. But that is something for the future. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
