aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* fixup changelogJon Leighton2012-07-071-1/+1
|
* Limit the number of records in Relation#inspectDamien Mathieu2012-07-061-2/+4
| | | | While it's interesting to have the results array, it can make a console or a webpage freeze if there are a lot of them. So this limits the number of records displayed in #inspect to 10 and tells how much were effectively found.
* Update release notes with AR::Relation#inspect change [ci skip]Carlos Antonio da Silva2012-07-061-3/+3
| | | | | See 07314e64fd62fb8e6165c8c539420160da9437e9. Also fix some tabs in AR Changelog.
* Show the records in Relation#inspectJon Leighton2012-07-061-6/+8
| | | | | | | | | | | | | | | | | The reason for removing the previous implementation of `#inspect` was that it hid from you that you were dealing with a `Relation` rather than an `Array`. But it is still useful to be able to see the records, particularly if you're writing something like the following in tests: assert_equal [foo], Post.where(:bar) If the assertion fails, you want to see what records were actually loaded. So this implementation makes it clear that you've got a `Relation`, but also shows your records.
* Add changelog entry for references statementsAleksey Magusev2012-07-031-0/+13
|
* Update 4.0 Release Notes with changelogs [ci skip]Carlos Antonio da Silva2012-07-021-3/+3
| | | | | | | Also fix some wrong formatting. Related discussion: https://github.com/rails/rails/commit/ab72040b74f742b6676b2d2a5dd029bfdca25a7a#commitcomment-1525256
* Unify the collation API for the database adptersRafael Mendonça França2012-07-011-2/+2
|
* Update AR and AP changelogs [ci skip]Carlos Antonio da Silva2012-06-301-1/+13
|
* Remove ActiveRelation#inspectBrian Cardarella2012-06-291-0/+4
|
* Added an entry about fda24312d3 in the CHANGELOG.kennyj2012-06-291-0/+15
|
* exists?(false) returns falseEgor Lynko2012-06-251-0/+4
| | | | `FinderMethods#exists?` finder method now returns *false* with the *false* argument
* Allow precision option for postgresql datetimesTony Schneider2012-06-221-0/+12
| | | | | | | | | | This patch addresses the difficulty of retrieving datetime fields. By default, the database holds a higher precision than the time as a String. This issue is discussed at length at the following links: - [#3519](https://github.com/rails/rails/issues/3519) - [#3520](https://github.com/rails/rails/issues/3520) Also, kudos to @mattscilipoti
* Fix changelog typo [ci skip]Carlos Antonio da Silva2012-06-221-1/+1
|
* Add changelog entry and guide updates for pluck with multiple columnsCarlos Antonio da Silva2012-06-221-0/+9
|
* It's AR::Reflection not AR::RelationAndrew White2012-06-221-1/+1
|
* Improve the derivation of HABTM assocation join table namesAndrew White2012-06-221-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improve the derivation of HABTM join table name to take account of nesting. It now takes the table names of the two models, sorts them lexically and then joins them, stripping any common prefix from the second table name. Some examples: Top level models (Category <=> Product) Old: categories_products New: categories_products Top level models with a global table_name_prefix (Category <=> Product) Old: site_categories_products New: site_categories_products Nested models in a module without a table_name_prefix method (Admin::Category <=> Admin::Product) Old: categories_products New: categories_products Nested models in a module with a table_name_prefix method (Admin::Category <=> Admin::Product) Old: categories_products New: admin_categories_products Nested models in a parent model (Catalog::Category <=> Catalog::Product) Old: categories_products New: catalog_categories_products Nested models in different parent models (Catalog::Category <=> Content::Page) Old: categories_pages New: catalog_categories_content_pages Also as part of this commit the validity checks for HABTM assocations have been moved to ActiveRecord::Reflection One side effect of this is to move when the exceptions are raised from the point of declaration to when the association is built. This is consistant with other association validity checks.
* Refactor and use class_attributeCarlos Antonio da Silva2012-06-181-4/+10
|
* Remember the stored attributes in a config attribute.Joost Baaij2012-06-181-0/+6
| | | | | | This allows you to retrieve the list of attributes you've defined. Usable for e.g. selects in the view, or interators based on the attributes you wish to store in the serialized column.
* Improve the CHANGELOG entry [ci skip]Rafael Mendonça França2012-06-181-2/+19
|
* Add CHANGELOG entry to composed_of removalRafael Mendonça França2012-06-181-0/+6
|
* Change minimum (default) log level in PostgreSQL to warning.kennyj2012-06-181-0/+6
|
* Add CHANGELOG entry to the uuid datatype support to PostgreSQL adpterRafael Mendonça França2012-06-141-0/+2
|
* registers the removal of update_attribute in the CHANGELOGXavier Noria2012-06-141-0/+6
|
* removes item in the Active Record CHANGELOGXavier Noria2012-06-141-2/+0
| | | | | | | That change to update_attribute was considered to be too subtle and was reverted in 30ea923 just before Rails 3 shipped. Later we introduced update_column (Rails 3.1).
* Use . instead of :: for class methods, add CHANGELOG entriesJosé Valim2012-06-101-0/+3
|
* + ActiveRecord::Base#destroy!Marc-Andre Lafortune2012-06-061-0/+5
|
* Sync CHANGLOG with the 3-2-stable branchRafael Mendonça França2012-06-011-0/+27
|
* Fix changelog example for count method with block [ci skip]Carlos Antonio da Silva2012-05-311-1/+1
| | | | Missed that too, thanks again @splattael.
* Yield only one argument instead of splatting.Carlos Antonio da Silva2012-05-281-0/+7
| | | | Add Changelog entry. Closes #4003
* Add support for CollectionAssociation#delete by Fixnum or StringFrancesco Rodriguez2012-05-281-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | I found the next issue between CollectionAssociation `delete` and `destroy`. class Person < ActiveRecord::Base has_many :pets end person.pets.destroy(1) # => OK, returns the destroyed object person.pets.destroy("2") # => OK, returns the destroyed object person.pets.delete(1) # => ActiveRecord::AssociationTypeMismatch person.pets.delete("2") # => ActiveRecord::AssociationTypeMismatch Adding support for deleting with a fixnum or string like `destroy` method.
* fix typo [ci skip]Jon Leighton2012-05-181-1/+1
|
* add changelogs about deprecated stuff [ci skip]Jon Leighton2012-05-181-1/+55
|
* Don't destroy readonly modelsJohannes Barre2012-05-171-0/+5
|
* Relation#from to accept other Relation objectsRadoslav Stankov2012-05-171-0/+7
| | | | Record.from("(#{sub_query.to_sql})") -> Record.from(sub_query) Record.from("(#{sub_query.to_sql}) a") -> Record.from(sub_query, :a)
* Fix misprint in AR changelogAlexey Vakhov2012-05-161-1/+1
|
* corrected some misspellingAngelo capilleri2012-05-151-3/+3
|
* Copy edit [ci skip]Rafael Mendonça França2012-05-131-0/+1
|
* Custom coders support for ActiveRecord::Store. JSON, YAML, Marshal can be ↵Andrey Voronkov2012-05-091-0/+6
| | | | used out of the box.
* Changelog entry regarding mysql(2) STRICT_ALL_TABLESMichael Pearson2012-05-051-0/+6
|
* Adding note about `first` and `take` to the changelogMarcelo Silveira2012-05-021-0/+6
|
* changelog fixes. Closes #3911Vijay Dev2012-05-011-13/+0
|
* Update Rails 3.2.3 release date in changelogs as March 30, 2012Michael de Silva2012-04-161-1/+1
| | | | | The release date details have been taken from http://weblog.rubyonrails.org/2012/3/30/ann-rails-3-2-3-has-been-released/
* Automatically create indexes for references/belongs_to statements in migrations.Joshua Wood2012-04-141-0/+22
|
* Add bang versions of relation query methods.Jon Leighton2012-04-121-0/+7
| | | | | The main reason for this is that I want to separate the code that does the mutating from the code that does the cloning.
* Add Relation#find_by and Relation#find_by!Jon Leighton2012-03-301-0/+10
|
* CHANGELOG entry for AR#sliceGuillermo Iguaran2012-03-291-0/+5
|
* Deprecate eager-evaluated scopes.Jon Leighton2012-03-211-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't use this: scope :red, where(color: 'red') default_scope where(color: 'red') Use this: scope :red, -> { where(color: 'red') } default_scope { where(color: 'red') } The former has numerous issues. It is a common newbie gotcha to do the following: scope :recent, where(published_at: Time.now - 2.weeks) Or a more subtle variant: scope :recent, -> { where(published_at: Time.now - 2.weeks) } scope :recent_red, recent.where(color: 'red') Eager scopes are also very complex to implement within Active Record, and there are still bugs. For example, the following does not do what you expect: scope :remove_conditions, except(:where) where(...).remove_conditions # => still has conditions
* Expand changelog and upgrading rails guide with IdentityMap infoCarlos Antonio da Silva2012-03-131-1/+10
|
* Remove IdentityMapCarlos Antonio da Silva2012-03-131-0/+2
|
* Add dynamic find_or_create_by_{attribute}! method.Andrew White2012-03-121-0/+2
|