Can anyone suggest a good design pattern for implementing field level security for a database system built on GAE and datastore. I'm not looking to adjust DS queries based on OU information per se, but may be; We are more looking for a way to define the data in the first place such that the security setting per attribute is retrievable without additional lookups.
Possible? Possible but hard? Bite the bullet and manage it by secondary lookups? Define custom datatypes? Thinking and shooting from the hip here really Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/JfWun8IeGsMJ. 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/google-appengine?hl=en.
