ggriffis/VittanaGinger
Public repository.
An app to demonstrate a One-to-Many (via has_one :through/has_many) database association. Using a through object is helpful when you want to store information specific to the association of two items—instead of just wanting to store the association itself. Using these helper methods the MANY side model will be cognizant of the ONE model but the ONE side model will not be directly cognizant of the MANY model. Both will be cognizant of the JOIN model, however. This is a rare scenario. Let’s use a bizarre, somewhat contrived, and controversial example. Let’s say we have a ONE side model, God. The MANY side model would be Human. Each God could have MANY Humans following him/her through a JOIN model of GuardianAngel. The God model could have many GuardianAngels but lets say s/he doesn’t care about keeping track of all his/her follower Humans. Who said DB associations were boring?
Public repository record indexed from GitHub. Explore verified star velocity metrics, source code repositories, and curated developer tool directories across the GitHubRepo ecosystem.
Public repository.
Public repository.
Public repository.
Public repository.