aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/active_record_querying.md
Commit message (Collapse)AuthorAgeFilesLines
* Small grammar fix in pluck descriptionJay Shepherd2014-08-121-1/+1
|
* [ci skip] Remove duplicated last! section.Juanito Fatas2014-07-161-17/+0
| | | | | | Reference: https://github.com/rails/rails/commit/d4fd0bd17709735ac91e434c94fe99429f078c6e cc @schneems
* [ci skip] Use appropriate mailer syntax.Juanito Fatas2014-07-161-3/+3
| | | | Reference: https://github.com/rails/rails/commit/f7e4362011ceb1317fd401125d48d7ccb9a1079c
* fix mismatched example call [ci skip]Vijay Dev2014-07-121-2/+2
|
* Revert "[ci skip] Fix doc for except"Vijay Dev2014-07-121-4/+5
| | | | | | | This reverts commit 0f6b101e09d210cea2494c5d4225760f1951ea67. Reason: It's better to let `unscope` be documented. We can add a separate section for `except`.
* [ci skip] remove invalid code from docsschneems2014-06-281-2/+0
|
* [ci skip] Fix doc for exceptschneems2014-06-281-5/+4
| | | | The example showed is `except`, however the method "documented" is `unstop`. Fix to align the docs to the example.
* [ci skip] Doc ability to chain in `find_each`schneems2014-06-281-1/+9
| | | | Also use appropriate mailer syntax in the `find_each` block.
* [ci skip] Consolidate docs for `find`schneems2014-06-281-25/+19
| | | | Put all options for overloading `find` in one section
* [ci skip] Consolidate docs for `last`schneems2014-06-281-16/+21
| | | | | | Add docs on what happens when a numerical argument is provided to last. Since `last!` behaves exactly the same way but can raise an argument we can consolidate it in the `last` section.
* [ci skip] Consolidate docs for `take`schneems2014-06-281-35/+20
| | | | | | Add docs on what happens when a numerical argument is provided to take. Since `take!` behaves exactly the same way but can raise an argument we can consolidate it in the `take` section.
* [ci skip] Consolidate docs for `find_by`schneems2014-06-281-19/+14
| | | | Since `find_by!` behaves exactly the same way but can raise an argument we can consolidate it in the `find_by` section.
* [ci skip] Consolidate docs for `first`schneems2014-06-281-35/+21
| | | | | | Add docs for `first` when provided a numerical argument. Since `first!` behaves exactly the same way but can raise an argument we can consolidate it in the `first` section.
* [ci skip] Add return values to examplesschneems2014-06-281-1/+10
|
* docs, update `includes` + `where` example in AR guide. [ci skip]Yves Senn2014-06-061-3/+16
| | | | Closes #15541.
* Remove docs regarding grouping multiple values, as we should avoidZachary Scott2014-06-011-18/+1
| | | | duplicating API reference in guides. Also :scissors: [ci skip]
* Add Total of grouped items to AR query interface on guidesMauro George2014-06-011-0/+34
| | | | [ci skip]
* Improve readability of Explain Queries table in guides [ci skip]John Kelly Ferguson2014-05-241-16/+36
|
* resolved reorder issue in rails active record guidepeeyush2014-05-231-2/+4
|
* Rename Posts to Articles in Guides, continuation of 2d446e77 / #13774 [ci skip]John Kelly Ferguson2014-05-211-84/+84
|
* fixes in active record query for reorderpeeyush2014-05-211-2/+2
|
* In Active Record Querying guide, currently `Merging of scopes` section uses ↵ariabov2014-04-021-30/+29
| | | | | | a concept of default scope in its example before it is introduced in the following section titled `Applying a default scope`. It makes more sense to switch the ordering to introduce default scopes (`Applying a default scope`) first and then go into `Merging of scopes` section where it is used.
* Fix a typo to make clause plural [ci skip]chriskohlbrenner2014-03-191-1/+1
|
* Don't use `# =>` when it is not the expression valuesRafael Mendonça França2014-02-181-8/+8
| | | | [ci skip]
* Fix the column name [ci skip]Rafael Mendonça França2014-02-181-2/+2
|
* Aesthetic [ci skip]Rafael Mendonça França2014-02-181-4/+4
|
* Tell default_scope are prepended [ci skip]Rafael Mendonça França2014-02-181-1/+1
|
* Updated doc for default scope [ci skip]Rashmi Yadav2014-02-181-4/+4
|
* Fix order syntax in find_by_sql exampleGreg Saks2014-01-261-1/+1
|
* Only some dynamic finders are deprecated.Rafael Mendonça França2014-01-161-5/+5
| | | | | | | find_by_* and find_by_*! are not deprecated for example, so lets add a note only where it is needed [ci skip]
* Update active_record_querying.mdGuillermo Iguaran2013-12-021-1/+1
| | | he or she => they
* Added `rewhere` usage to AR querying guidesVipul A M2013-11-251-0/+26
|
* Merge remote-tracking branch 'docrails/master'Xavier Noria2013-11-241-5/+5
|\ | | | | | | | | | | Conflicts: activesupport/lib/active_support/core_ext/hash/deep_merge.rb activesupport/lib/active_support/core_ext/hash/keys.rb
| * Improve reading / style of hashes in AR guideCarlos Antonio da Silva2013-11-191-5/+5
| |
| * Revert last two commits mistakenly changing join/include syntaxCarlos Antonio da Silva2013-11-191-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | --- Revert "syntax error joining/including models" This reverts commit ac35f72f30c47298a20a90c8c537db888b463bbb. --- Revert "syntax error joining tables" This reverts commit c365986b48c3e8bc8c7f3fa6a8521616ed5dc138. --- Comments: https://github.com/rails/docrails/commit/c365986b48c3e8bc8c7f3fa6a8521616ed5dc138#commitcomment-4630684
| * syntax error joining/including modelsSergio2013-11-181-2/+2
| | | | | | syntax error joining/including models
| * syntax error joining tablesSergio2013-11-181-5/+5
| | | | | | syntax error joining tables
* | Fix ActiveRecord::Relation#unscopeJon Leighton2013-11-201-16/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I'm pretty confused about the addition of this method. The documentation says that it was intended to allow the removal of values from the default scope (in contrast to #except). However it behaves exactly the same as except: https://gist.github.com/jonleighton/7537008 (other than having a slightly enhanced syntax). The removal of the default scope is allowed by 94924dc32baf78f13e289172534c2e71c9c8cade, which was not a change we could make until 4.1 due to the need to deprecate things. However after that change #unscope still gives us nothing that #except doesn't already give us. However there *is* a desire to be able to unscope stuff in a way that persists across merges, which would allow associations to be defined which unscope stuff from the default scope of the associated model. E.g. has_many :comments, -> { unscope where: :trashed } So that's what this change implements. I've also corrected the documentation. I removed the guide references to #except as I think unscope really supercedes #except now. While we're here, there's also a potential desire to be able to write this: has_many :comments, -> { unscoped } However, it doesn't make sense and would not be straightforward to implement. While with #unscope we're specifying exactly what we want to be removed from the relation, with "unscoped" we're just saying that we want it to not have some things which were added earlier on by the default scope. However in the case of an association, we surely don't want *all* conditions to be removed, otherwise the above would just become "SELECT * FROM comments" with no foreign key constraint. To make the above work, we'd have to somehow tag the relation values which get added when evaluating the default scope in order to differentiate them from other relation values. Which is way too much complexity and therefore not worth it when most use cases can be satisfied with unscope. Closes #10643, #11061.
* | Change Relation#all to Relation#load [ci skip]Sıtkı Bağdat2013-11-151-1/+1
|/
* Merge branch 'master' of github.com:rails/docrailsVijay Dev2013-09-281-1/+1
|\
| * use active voice and use more descriptive termsWeston Platter2013-09-221-1/+1
| |
* | quote `false` reference in querying guide.Yves Senn2013-09-261-1/+1
| |
* | [ci skip] Correct the explanation of the example for find_or_create_by when ↵Daniel Lissner2013-09-251-1/+1
|/ | | | used with create_with in ActiveRecord Querying guide
* Merge branch 'master' of github.com:rails/docrailsVijay Dev2013-09-131-6/+10
|\
| * added # or commentSergio2013-09-051-1/+1
| |
| * Review the changes made on 90155b4e28a3887dce9428e9df150ede3d6c7465Rafael Mendonça França2013-09-041-5/+9
| |
| * Client.exists?(1,2,3) and Client.exists?([1,2,3]) does not workSergio2013-09-051-3/+3
| | | | | | | | The right command for doing that is Client.exists?id:[1,2,3] Exists does not work like find method, in find method you can do Person.find(1, 2, 6) or Person.find([7, 17]) but not Person.exists?(1,2,3) or Person.exists?([1,2,3])
| * Example of Join modelsSergio2013-09-041-1/+1
| | | | | | In the example of join models, there are five models but in the explanation only consider Category, Post, Comment and Guest.
* | Document a difference between pluck and select [ci skip]Eugene Gilburg2013-09-041-2/+33
|/ | | | Explain that `pluck` differs from `select` in that it does not construct `ActiveRecord` objects and thus model-level overrides are unavailable.
* Add examples of AR order method's hash notation to Rails Guide [ci skip]Sugino Yasuhiro2013-08-221-0/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-12 22:13:42 +0000