You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a resource called edition that match the various editions of the workshop. There should be a separate record for January-2015 edition, and a separate one for Nov-2014 and so on.
Edition model will have a name and date, and a small CRUD interface for the admin
The home page will only show the upcoming edition, or the just passed one
Shouldn't the relationships be more of has_many through? Coz there can be many editions - and each participant/coach can be associated with more than 1 edition.
On 15-Jan-2015, at 2:35 pm, Vijay Aravamudhan [email protected] wrote:
Shouldn't the relationships be more of has_many through? Coz there can be many editions - and each participant/coach can be associated with more than 1 edition.
—
Reply to this email directly or view it on GitHub.
We need a resource called edition that match the various editions of the workshop. There should be a separate record for January-2015 edition, and a separate one for Nov-2014 and so on.
Edition
model will have aname
anddate
, and a small CRUD interface for the adminThe home page will only show the upcoming edition, or the just passed one
Here's its associations:
And also a migration script that attaches all the existing participants to the Nov edition
The text was updated successfully, but these errors were encountered: