On Thursday, May 31, 2018 at 5:32:37 PM UTC+2, Jeremy Evans wrote: > > Not sure off hand why it would be required for that association. I could > probably tell you if you provide the full backtrace so I can see what is > calling Employee#pk. >
Thanks! I'll try it and get back to you. > Really, if you want the data to be read only, the best way to handle that > is to enforce it in the database via database permissions (GRANT/REVOKE). > Overriding Model#save/update/delete is only a partial fix. > Since this is a materialized view Postgres would throw an error in any case since you can neither insert/update/delete. I'm not sure if this shone through properly in my question, but this "model" represents a (materialized) view. I'm not sure if that _really_ makes sense for an ORM. Happy to hear other suggestions! Thank you so much for your time helping out and your lovely gems! -- 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.
