Rumbaugh’s statement is the most telling and Uncle Bob’s good advice. As I’ve said elsewhere, Aggregation is semantically so weak as to offer nothing practically beneficial. It only has one valid corner case (acyclicity of recursive relationships) however few people know and understand that. So you end up having to point out in comments anyway. … Read more
Or you can use the built-in Blue Bird Promise feature to make it. (Working on Sails@v0.10.5) See the codes below: var _ = require(‘lodash’); … Post .findOne(req.param(‘id’)) .populate(‘user’) .populate(‘comments’) .then(function(post) { var commentUsers = User.find({ id: _.pluck(post.comments, ‘user’) //_.pluck: Retrieves the value of a ‘user’ property from all elements in the post.comments collection. }) .then(function(commentUsers) … Read more
Please take a look at this answer. What used to be @company = Company.find_or_create_by_name(name) in Rails 4 is now @company = Company.find_or_create_by(name: name) Another way to do this in Rails 4 would be: @company = Company.where(name: name).first_or_create
For 1) show do panel “Patients” do table_for physician.appointments do column “name” do |appointment| appointment.patient.name end column :appointment_date end end end For 2) form do |f| f.inputs “Details” do # physician’s fields f.input :name end f.has_many :appointments do |app_f| app_f.inputs “Appointments” do if !app_f.object.nil? # show the destroy checkbox only if it is an existing … Read more
alias_method is your friend here. alias_method :original_bar, :bar def bar self.original_bar || Bar.last end The way this works is that you alias the default “bar” method as “original bar” and then implement your own version of “bar”. If the call to original_bar returns nil then you return the last Bar instance instead.
Try the following: belongs_to :city, optional: true According to the new docs: 4.1.2.11 :optional If you set the :optional option to true, then the presence of the associated object won’t be validated. By default, this option is set to false.
Edit: Rails 3.1 supports nested associations. E.g: has_many :tasks has_many :assigments, :through => :tasks has_many :users, :through => :assignments There is no need for the solution given below. Refer to this screencast for more details. Original Answer You are passing a has_many :through association as a source for another has_many :through association. I don’t think … Read more
belongs_to association expect an association_id column in its corresponding table. Since cars belongs_to user, the cars table should have a user_id column. This can be accomplished 2 ways. first, you can generate the column when you create the model rails g model car user_id:references or just add the user_id after you create the model like … Read more
Logic, OK it might sound a bit weak for this but it would be logical to say that “I have a supplier who has an account with me, I want to see the entire account history of this supplier”, so it makes sense for me to be able to access account history from supplier directly. … Read more
You can perform a query like this: Report.joins(:servers).where(:servers => {:company_id => 5}) To me, this is the cleaner solution to raw SQL.