aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/active_record_querying.md
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Merge branch 'master' of github.com:rails/docrailsVijay Dev2013-08-171-7/+1
|\ | | | | | | | | | | | | | | Conflicts: actionview/README.rdoc activerecord/lib/active_record/migration.rb guides/source/development_dependencies_install.md guides/source/getting_started.md
| * Revert "Merge branch 'master' of github.com:rails/docrails"Vijay Dev2013-08-171-7/+1
| | | | | | | | | | | | | | This reverts commit 70d6e16fbad75b89dd1798ed697e7732b8606fa3, reversing changes made to ea4db3bc078fb3093ecdddffdf4f2f4ff3e1e8f9. Seems to be a code merge done by mistake.
* | Revert change on ActiveRecord::Relation#order method that prepends newRafael Mendonça França2013-07-291-2/+2
|/ | | | | | | | | | | | | | | order on the old ones The previous behavior added a major backward incompatibility since it impossible to have a upgrade path without major changes on the application code. We are taking the most conservative path to be consistent with the idea of having a smoother upgrade on Rails 4. We are reverting the behavior for what was in Rails 3.x and, if needed, we will implement a new API to prepend the order clauses in Rails 4.1.
* Add a SQL example for `not` [ci skip]Robin Dupret2013-07-261-1/+7
| | | | To share a certain logic across other examples, let's add a sample SQL code generated by the given Ruby code
* Revert "Fix SyntaxError in guides sample code"Erich Kist2013-07-181-1/+1
| | | | | | | | This reverts commit f573df32d43c413a5098721ba6151ff190c23c6c. The original idea of this documentation was to showcase the feature where you can remove some only queries attributes with a single key-value pair.
* Fix SyntaxError in guides sample codeAkira Matsuda2013-07-081-1/+1
| | | | [ci skip]
* 1.9 Hash SyntaxAkira Matsuda2013-07-081-1/+1
|
* removed markdown code markers which were rendering in the generated AR ↵Brian Foshee2013-07-041-2/+0
| | | | querying guide
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2013-06-261-1/+1
|\ | | | | | | | | Conflicts: guides/source/layout.html.erb
| * reorder finder methods list alphabeticallyMikhail Dieterle2013-06-161-1/+1
| |
* | Added an example of the query without except before the example with exceptPrathamesh Sonpatki2013-06-141-0/+8
|/
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2013-06-141-2/+2
|\ | | | | | | | | Conflicts: guides/source/upgrading_ruby_on_rails.md
| * Remove double spaces in code examplesSunny Ripert2013-05-281-1/+1
| |
| * In rails 4 there are much more ways to retrieve a single objectMikhail Dieterle2013-05-221-1/+1
| |
* | Missing ending ``` at 14.2 Merging of scopesLeo Gallucci2013-05-191-0/+1
|/ | | http://edgeguides.rubyonrails.org/active_record_querying.html#merging-of-scopes
* Rails 4 has deprecated :order in has_many to use a lambda instead, update ↵Nick Quaranto2013-05-011-1/+1
| | | | the guide accordingly
* it's Active Record not ActiveRecordYves Senn2013-04-301-1/+4
| | | | /cc @fxn
* Mention that Dynamic finders have been deprecated in Rails 4Jonathan Roes2013-04-231-0/+2
|
* more Ruby 1.9 Hash syntax in our guidesYves Senn2013-04-151-1/+1
|
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2013-03-301-9/+5
|\ | | | | | | | | | | | | | | | | Conflicts: activerecord/lib/active_record/connection_adapters/abstract/schema_statements.rb activerecord/test/cases/adapter_test.rb guides/source/testing.md [ci skip]
| * Update documentation for Where chained modifiers.Ryan Sandridge2013-03-191-7/+3
| | | | | | | | | | where.like and where.not_like were removed in 8d02afeaee, but the guide was not updated.
| * do some typo fixingVipul A M2013-03-141-1/+1
| |
| * I think "uniq" is more Rails-y than select("distinct(categories.id)")capps2013-03-111-1/+1
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 20:00:41 +0000