Maybe read-only is the wrong word. I basically just want to prevent changes 
from being saved. #freeze may be a step too far as I don't necessarily care 
if the data changes, as long as it's not committed to the database.

On Friday, 30 September 2016 09:39:41 UTC+10, Tom Wardrop wrote:
>
> Is it possible to make a Model, either at the class or instance level 
> (preferrably class) read-only? Well, of course it's possible, so maybe I 
> should ask, what's the best method of doing this, e.g. a #validate method 
> that always return false, a before_save hook that throws an exception?
>
> Thanks,
> Tom
>

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.

Reply via email to