aboutsummaryrefslogtreecommitdiffstats
path: root/activemodel/activemodel.gemspec
diff options
context:
space:
mode:
authorJames Doyley <jdoyley@gmail.com>2015-11-24 15:02:23 +0000
committerJames Doyley <jdoyley@gmail.com>2016-01-18 10:08:43 +0000
commitf72fe2d5a65002195c15a0cfe3ae3c51db825d36 (patch)
treed9454561feae4cf4d17eb98d0872196916833963 /activemodel/activemodel.gemspec
parent58cea7f2dc7426c3f7445adfb8925880ec1b3644 (diff)
downloadrails-f72fe2d5a65002195c15a0cfe3ae3c51db825d36.tar.gz
rails-f72fe2d5a65002195c15a0cfe3ae3c51db825d36.tar.bz2
rails-f72fe2d5a65002195c15a0cfe3ae3c51db825d36.zip
Updated the guides for having a distinct has_many through at the database level
The current example add_index :person_articles, :article, unique: true Does not work, the `:article` column does not exist as it will be a join table (based on the prior example) so should use :article_id The documentation seems to suggest that it will allow an article to be added only once to a person via the join table, what actually occurs is that it only allows the article to be added to one person, at which point it should be a `belongs_to` association. Also changed the new example to use readings based on the prior example
Diffstat (limited to 'activemodel/activemodel.gemspec')
0 files changed, 0 insertions, 0 deletions