Hi Jeremy, Thank you for your excellent response. I guess I convinced myself that the access control belonged in the model and that I should be asking either User or the resource what is allowed.
I would still like to move to a solution that stores procs, so I can avoid having to a) string together an array of symbols and b) having a separate key for datasets that have arguments (current user). I guess storing an array of allowed fields makes sense and would fit with either field solution. I constantly grumble about how Sinatra's params hash, for example, only deletes keys if they are referenced as strings, but with allow key access. An easy source of confusion. I will work further on this sketch and ping you if you're interested. Thank for both sequel and for, seriously, some of the fastest and most thorough support/answers I've ever received. Jamie -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en.
