Comments on: Read-only Models in ActiveRecord

By: zobie

zobie — Tue, 11 Oct 2011 08:12:14 +0000

I agree that enforcing constraints at the database level is a good approach. For the specific project I was working on when I wrote this article, I did not have access to make changes to the database itself. Because I tend to be paranoid, I wanted some assurance that data wasn’t accidentally modified.

By: pascal

pascal — Sun, 09 Oct 2011 14:56:09 +0000

why not ensure read only access on the db layer through proper user rights?
this would be more secure (your solution does not cover native sql)

pascal

By: jmartorella

jmartorella — Tue, 28 Dec 2010 01:29:15 +0000

Thanks for this post. I was doing something quite similar and found that you can still call delete and delete_all, as they do not use callback methods. You can override those methods on your read only model and raise the ReadOnly exception in the exact same way:

def self.delete_all raise ActiveRecord::ReadOnlyRecord end

def delete raise ActiveRecord::ReadOnlyRecord end

By: WT

WT — Sat, 27 Nov 2010 21:53:27 +0000

Thanks,

I’m using this with a materialized view that gets updated by plpgsql database functions and triggers.

By: zobie

zobie — Fri, 27 Feb 2009 23:14:42 +0000

I’m really glad that it was helpful to you Jeremy!

By: Jeremy Walworth

Jeremy Walworth — Fri, 27 Feb 2009 23:05:21 +0000

Thanks for this post! It came up on a Google search for “activerecord and readonly”. I have a situation where a proposal is generated, and after that, several records need to be locked down. This is perfect for that!