Steve’s answer works but since the instance is of class BaseUser when save is called, validations and callbacks defined in User will not run. You’ll probably want to convert the instance using the becomes method: user = BaseUser.where(email: “[email protected]”).first_or_initialize user = user.becomes(User) # convert to instance from BaseUser to User user.type = “User” user.save!
From: http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html :touch If true, the associated object will be touched (the updated_at/on attributes set to now) when this record is either saved or destroyed. If you specify a symbol, that attribute will be updated with the current time in addition to the updated_at/on attribute. belongs_to :company, :touch => true belongs_to :company, :touch => :employees_last_updated_at
I’m not sure the new respond_to/respond_with style is flexible enough to do this. It very well may be, but as far as I understand, it’s meant to simplify only the simplest cases. You can achieve what you are trying to do with the old-style respond_to with a block, however, by passing parameters to to_json. Try … Read more
To a first approximation: ActiveRecord::Base.connection.query_cache.clear
Try: current_user.items.exists?(params[:id]) Or current_user.items.exists?(@item.id)
There are four types of callbacks accepted by the callback macros: Method references (symbol), callback objects, inline methods (using a proc), and inline eval methods (using a string). Try this? after_update -> { cache_bust(true) }
By issuing rake -T you have the following database tasks: rake db:create # Create the database from DATABASE_URL or config/database.yml for the current Rails.env (use db:create:all to create all dbs in the config) rake db:drop # Drops the database using DATABASE_URL or the current Rails.env (use db:drop:all to drop all databases) rake db:fixtures:load # Load … Read more
Since MySQL indexes are already case-insensitive, I’m guessing you’re dealing with PostgreSQL, which creates case-sensitive indexes by default. I’m answering here based on Rails 3.2.3 and PostgreSQL 8.4. It seems functional indexes are one more example of things that ActiveRecord can’t generate. Foreign keys and UUID columns are two more that come to mind. So … Read more
Translating @TuteC into ActiveRecord: sql=”SELECT id, COUNT(id) as quantity FROM types GROUP BY name HAVING quantity > 1″ #=> Type.select(“id, count(id) as quantity”) .group(:name) .having(“quantity > 1”)
The error occurs due to the following security update in Rails: https://discuss.rubyonrails.org/t/cve-2022-32224-possible-rce-escalation-bug-with-serialized-columns-in-active-record/81017 The Hash serializer apparently loaded data with YAML.unsafe_load, which now changed to YAML.safe_load. This new method does not handle data types such as Symbol or Time by default for security reasons. The workaround as the announcement suggests is to either migrate the serializer … Read more