The only difference is that in 3.2, when you add timestamps, they are marked as NOT NULL. I am -1 on adding more complexity to habtm to support this.My opinion is that if people want additional attributes on a join table they should use hm:t.update_attribute Updates a single attribute and saves the record without going through the normal validation procedure.
The regular update_attribute method in Base is replaced with this when the validations module is mixed in, which it is by default.
Also note that Validation Use update_attribute to skip validations.
update_column(name, value) Updates a single column in a database, without calling save.
The latter one is set to the current time when a dataset is created and the first one is set to the current time when a dataset gets updated.
update_attribute uses save(false) while update_attributes uses save (which means save(true)).
Callbacks If perform_validation is false while calling save then it skips validation, and it also means that all the before_* callbacks associated with save.For a work project I had to update some values (a lock field for example) w/o updating these magic columns.After doing some research on the interwebs there are several solutions: This was the first and easiest one.Excepted from this license are code snippets that are explicitely marked as citations from another source.The MIT License (MIT) Copyright (c) 2013-2017 makandra Gmb H Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.Inserting records manually will auto-populate those columns too.