Rails doesn’t have the facility to pass the options for include query. But we can pass these params with the association declaration under the model. For your scenario, you need to create a new association with users model under the profile model, like below belongs_to :user_only_fetch_email, :select => “users.id, users.email”, :class_name => “User” I just … Read more
You’re looking for reflect_on_all_associations. So in short: Post.reflect_on_all_associations(:has_many) …will give an array (of object with attributes like name, etc) of all has_many associations.
Add in your gemfile: gem ‘validates_email_format_of’ and in your model: validates :email, email_format: { message: “doesn’t look like an email address” } Or if you don’t want use a gem, use regex: validates_format_of :email, :with => /\A([^@\s]+)@((?:[-a-z0-9]+\.)+[a-z]{2,})\z/i
You can implement your own method in your model. Something like this def valid_attribute?(attribute_name) self.valid? self.errors[attribute_name].blank? end Or add it to ActiveRecord::Base
Your question is (almost) exactly answered in the Rails guides. Here’s the example code they give. This class validates that the date is in the past, while your question is how to validate that the date is in the future, but adapting it should be pretty easy: class Invoice < ActiveRecord::Base validate :expiration_date_cannot_be_in_the_past def expiration_date_cannot_be_in_the_past … Read more
Update Rails 6.1 With the new Rails version this becomes simple, as described here: .where.missing(:children) For older versions see below. Rails 3 & 4 scope :without_children, includes(:children).where(:children => { :id => nil }) The big difference here is the joins becoming a includes: an include loads all the relations, if they exists, the join will … Read more
As per the API Documentation, it is a method that only updates the specified timestamps of the model with the current time. So in order to update the updated_at field: product.touch or to update the updated_at and designed_at fields: product.touch(:designed_at) Now, I have never used this method before, but I’d think it would be useful … Read more
Seems primary key is missing for the table collections. Prior to Rails 3.2, set the primary key in model like class Collection < ActiveRecord::Base set_primary_key “my_existing_column” end In Rails 3.2+ and Rails 4, set the primary key in model like class Collection < ActiveRecord::Base self.primary_key = “my_existing_column” end OR We can alter the table and … Read more
Your migration will work and will allow multiple null values (for the most database engines). But your validation for the user class should look like below. validates :email, uniqueness: true, allow_nil: true
I think the best solution would be: Author.includes(:articles).where(:articles=>{published: true}).find(params[:author_id]) Or you can create scope: class Author < ActiveRecord::Base scope :with_published_articles, -> { includes(:articles).where(articles: { published: true}) } end and then: Author.with_published_articles.find(params[:author_id].to_s)