Rails update attributes not validating
The MIT License (MIT) Copyright (c) 2010-2011 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.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.This is especially useful if you want to persist the changed class in your database.Note: The old instance's sti column value will be changed too, as both objects share the same set of attributes.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.update_column(name, value) Updates a single column in a database, without calling save.This also allows you to create non-table attributes that affect the record.
If you have overridden the setter to add functionality, it will be called.
Note: The new instance will share a link to the same attributes as the original class.
Therefore the sti column value will still be the same.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
This means your comment be automatically sent into moderation and you won't receive emails when a user replies.