I’m looking for a solution to the following problem: I have an ActiveRecord entity that is backed by an updatable database view (in DB2 via the activerecord-jdbc-adapter gem). This view contains one column that is calculated from other columns and is ‘read-only’: you cannot set that column in any valid way. When a new record is created for this entity, that field should not be set. However, by default, ActiveRecord does set it with the ‘default’ (NULL), which is rejected by the database.
attr_readonly isn’t a solution, because that only excludes a column from updates and not from creates.
attr_ignore, such as implemented by the ‘lincoln’ gem, is not a solution either, because then the field is ignored entirely. However, the column still needs to be read and be accessible. It’s actually even used as part of a relation.
There are ways to prevent you from setting a certain attribute of an ActiveRecord entity, but that doesn’t usually prevent that attribute from being included in create or update statements
Does anyone know if there is a way in ActiveRecord to specify a column as ‘never set this field’?
Update, in response to Arsen7:
I’ve attempted to use the after_initialize hook to remove the attribute from a newly created entity, so it isn’t included in the SQL that is built. The trouble with this is that the attribute is completely removed and not available anymore at all, pretty much identical to the ‘igonre_attr’ situation described above. Due to caching, that’s not trivial to get around and would require additional logic to force a reload of entities of these specific tables. That can probably be achieved by overriding create to add a ‘reload’, in addition to using the after_initialize.
(As pointed out by Arsen7, I forgot to mention I’m at ActiveRecord 3.0.9)
My solution
Since my entities already inherit from a subclass of ActiveRecord::Base, I’ve opted to add before_create and after_create hooks. In the before_create hook, I remove the ‘calculated’ columns from the @attributes of the instance. In the after_create hook, I add them again and read the values of the ‘calculated’ columns from the database to set them to the values they received.
Adding such hooks is almost identical to overriding create, so I consider Arsen7’s answer to be correct.
I’m afraid ActiveRecord is not prepared for the use case you need. (By the way: which version of AR are you using?)
But I believe you may apply two possible workarounds.
The first, is to overwrite the ‘create’ method of your model, executing some other SQL, prepared manually in the worst case. I suppose that the real function which will need to be overwritten will not be the ‘create’ itself, but looking at the sources you could find the one.
The other solution, and I believe, a more elegant one, would be to create a trigger in the database. I am more in the PostgreSQL world, where I would use a
'CREATE RULE', but looking at the DB2 documentation I see that in DB2 there are ‘INSTEAD OF’ triggers. I hope this may be helpful.