As I haven’t used Rails in a year or two (and even then, only a few small side projects to learn the language for fun) I tend to run across your typical “new to the language” syntax nuances relatively frequently. Typically a quick Google gets me an answer and I can move on (can’t imagine what debugging was like 20 years ago…) but this past weekend I was running into an issue while building a relatively simple time tracking application in Rails that I thought might be helpful for anyone else starting up.
This particular use case revolved around creating Timesheets and the Time Entries that fall within them. In this case, Timesheet can have many Time Entries, but we want to ensure that a Time Entry belongs to a Timesheet. Below are my original models (stripped of any of the implementation irrelevant to this post).
class Timesheet < ActiveRecord::Base has_many :time_entries end class TimeEntry < ActiveRecord::Base belongs_to :timesheet validates :timesheet_id, :presence => true end
I then went about building a simple HTML page that allowed editing of both the Timesheet and the related Time Entries in a single form, and upon submission would create both the parent and child with a single save invocation on the Timesheet. Below is the simplest form of the controller and html.erb file.
class TimesheetsController < ApplicationController def new @timesheet = @user.timesheets.new 2.times do # Testing with 2 empty rows @timesheet.time_entries.build end end end <%= form_for(@timesheet) do |f| %> <%= f.date_select :start_date %> <%= f.date_select :end_date %> <%= f.fields_for :time_entries do |entry| %> <%= entry.date_select :completion_date %> <%= entry.text_field :notes %> <% end %> <%= f.submit "Submit" %> <% end %>
However, when I would click submit the creation of the child Time Entry records were failing.
ActiveRecord::RecordInvalid: Validation failed: Time entries timesheet can’t be blank
The implication here was that the timesheet_id field on the Time Entry was not being set implicitly during the save context on the timesheet.
After searching around a bit (more accurately, trying to find the right words to Google), I came across a StackOverflow post that got me on the right track. The issue was that I was trying to validate that the foreign key on Time Entry for Timestamp existed using validates_presence rather than using inverse_of in the relationship declaration. The official documentation around the best practice is here.
After making the tweak to my object model, I finally was successful.
class TimeEntry < ActiveRecord::Base belongs_to :timesheet, :inverse_of => :time_entries end