mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Fix documentation
The docs for disable joins had intermingled with the docs for through. I think that this happened in a merge conflict/rebase.
This commit is contained in:
parent
4493db2109
commit
69dfa29135
1 changed files with 10 additions and 13 deletions
|
@ -1387,11 +1387,6 @@ module ActiveRecord
|
|||
# of association, including other <tt>:through</tt> associations. Options for <tt>:class_name</tt>,
|
||||
# <tt>:primary_key</tt> and <tt>:foreign_key</tt> are ignored, as the association uses the
|
||||
# source reflection.
|
||||
# [:disable_joins]
|
||||
# Specifies whether joins should be skipped for an association. If set to true, two or more queries
|
||||
# will be generated. Note that in some cases, if order or limit is applied, it will be done in-memory
|
||||
# due to database limitations. This option is only applicable on `has_many :through` associations as
|
||||
# `has_many` alone do not perform a join.
|
||||
#
|
||||
# If the association on the join model is a #belongs_to, the collection can be modified
|
||||
# and the records on the <tt>:through</tt> model will be automatically created and removed
|
||||
|
@ -1403,6 +1398,11 @@ module ActiveRecord
|
|||
# join model. This allows associated records to be built which will automatically create
|
||||
# the appropriate join model records when they are saved. (See the 'Association Join Models'
|
||||
# section above.)
|
||||
# [:disable_joins]
|
||||
# Specifies whether joins should be skipped for an association. If set to true, two or more queries
|
||||
# will be generated. Note that in some cases, if order or limit is applied, it will be done in-memory
|
||||
# due to database limitations. This option is only applicable on `has_many :through` associations as
|
||||
# `has_many` alone do not perform a join.
|
||||
# [:source]
|
||||
# Specifies the source association name used by #has_many <tt>:through</tt> queries.
|
||||
# Only use it if the name cannot be inferred from the association.
|
||||
|
@ -1553,14 +1553,6 @@ module ActiveRecord
|
|||
# source reflection. You can only use a <tt>:through</tt> query through a #has_one
|
||||
# or #belongs_to association on the join model.
|
||||
#
|
||||
# If you are going to modify the association (rather than just read from it), then it is
|
||||
# a good idea to set the <tt>:inverse_of</tt> option.
|
||||
# [:disable_joins]
|
||||
# Specifies whether joins should be skipped for an association. If set to true, two or more queries
|
||||
# will be generated. Note that in some cases, if order or limit is applied, it will be done in-memory
|
||||
# due to database limitations. This option is only applicable on `has_one :through` associations as
|
||||
# `has_one` alone does not perform a join.
|
||||
#
|
||||
# If the association on the join model is a #belongs_to, the collection can be modified
|
||||
# and the records on the <tt>:through</tt> model will be automatically created and removed
|
||||
# as appropriate. Otherwise, the collection is read-only, so you should manipulate the
|
||||
|
@ -1571,6 +1563,11 @@ module ActiveRecord
|
|||
# join model. This allows associated records to be built which will automatically create
|
||||
# the appropriate join model records when they are saved. (See the 'Association Join Models'
|
||||
# section above.)
|
||||
# [:disable_joins]
|
||||
# Specifies whether joins should be skipped for an association. If set to true, two or more queries
|
||||
# will be generated. Note that in some cases, if order or limit is applied, it will be done in-memory
|
||||
# due to database limitations. This option is only applicable on `has_one :through` associations as
|
||||
# `has_one` alone does not perform a join.
|
||||
# [:source]
|
||||
# Specifies the source association name used by #has_one <tt>:through</tt> queries.
|
||||
# Only use it if the name cannot be inferred from the association.
|
||||
|
|
Loading…
Reference in a new issue