Yes it works, but I think lambda: has_membership is much better approach as pointed by Anthony as more fast since the lambda is only hit when you really want to access the records...
Richard On Mon, Jun 4, 2012 at 4:00 PM, pbreit <pbreitenb...@gmail.com> wrote: > I might not quite understand the question but wouldn't readable/writable > work? > > > On Monday, June 4, 2012 5:56:40 AM UTC-7, bob wrote: >> >> >> In the old days I would just create a database view on a subset of a >> table that I wanted to allow other developers to access (assuming read >> only), however I'm not sure if that's the best thing to do with web2py. >> >> I have a table that has: >> >> last_name >> first_name >> etc >> including some 'internal' columns that I don't want to expose on any form >> or service. >> >> Any thoughts on the best way to implement this? >> >> I'm thinking: >> >> a: database view (postgresql in this case), issues being no 'id' in >> the view and I'm not sure how best to maintain that. >> >> b: a new .py that takes the full record and returns the subset. >> upside - it would be a single point of maintenance, question is where >> would this live (in the models, it's not a controller so it doesn't really >> fit there)? >> >> c: ?? >> >> thanks for any suggestions, >> bobm >> >>
