aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #7352 from aripollak/microsecond-timestampRafael Mendonça França2012-08-171-0/+6
|\ | | | | Fix occasional microsecond conversion inaccuracy
| * Fix occasional microsecond conversion inaccuracyAri Pollak2012-08-151-0/+6
| | | | | | | | | | | | | | | | | | ActiveRecord::ConnectionAdapters::Column#microseconds did an unnecessary conversion to from Rational to float when calculating the integer number of microseconds. Some terminating decimal numbers in base10 are repeating decimal numbers in base2 (the format of float), and occasionally this causes a rounding error. Patch & explanation originally from Logan Bowers.
* | Renaming active_record_deprecated_finders to activerecord-deprecated_findersJon Leighton2012-08-171-2/+2
|/ | | | For consistency with the other AR extension plugins we are creating.
* Remove duplicated changelog entry [ci skip]Carlos Antonio da Silva2012-08-151-6/+0
|
* Move changelog entry to the top [ci skip]Carlos Antonio da Silva2012-08-151-5/+4
|
* Merge pull request #7133 from roshats/fix_update_all_with_blank_argumentCarlos Antonio da Silva2012-08-151-0/+4
|\ | | | | | | Change Relation#update_all with blank argument to raise an ArgumentError instead of trying an update with empty fields.
| * raise ArgumentError if list of attributes to change is empty in update_allRoman Shatsov2012-08-141-0/+4
| |
* | Restore state on create when ActiveRecord::RecordInvalid is raisedDave Yeu2012-08-111-0/+5
| | | | | | | | This fixes issue #3217.
* | Sync CHANGELOGs [ci skip]Rafael Mendonça França2012-08-111-3/+83
| |
* | Added changelog entry for table name prefix fix [ci skip]Wojciech Wnętrzak2012-08-111-0/+3
| |
* | Remove the dependent_restrict_raises option.Jon Leighton2012-08-101-16/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's not really a good idea to have this as a global config option. We should allow people to specify the behaviour per association. There will now be two new values: * :dependent => :restrict_with_exception implements the current behaviour of :restrict. :restrict itself is deprecated in favour of :restrict_with_exception. * :dependent => :restrict_with_error implements the new behaviour - it adds an error to the owner if there are dependent records present See #4727 for the original discussion of this.
* | Merge pull request #7140 from seamusabshere/patch-1Rafael Mendonça França2012-08-051-0/+5
|\ \ | | | | | | | | | | | | Make sure :environment task is executed before db:schema:load or db:structure:load
| * | Update changelogRafael Mendonça França2012-08-051-0/+5
| |/
* | Remove ActiveRecord::Base.to_aJon Leighton2012-08-031-2/+1
| | | | | | | | | | On reflection, it seems like a bit of a weird method to have on ActiveRecord::Base, and it shouldn't be needed most of the time anyway.
* | reinstate changelog that seems to have been accidentally deleted o_OJon Leighton2012-08-031-0/+19
| |
* | Allow Relation#merge to take a proc.Jon Leighton2012-08-031-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was requested by DHH to allow creating of one's own custom association macros. For example: module Commentable def has_many_comments(extra) has_many :comments, -> { where(:foo).merge(extra) } end end class Post < ActiveRecord::Base extend Commentable has_many_comments -> { where(:bar) } end
* | Add CollectionProxy#scopeJon Leighton2012-08-011-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This can be used to get a Relation from an association. Previously we had a #scoped method, but we're deprecating that for AR::Base, so it doesn't make sense to have it here. This was requested by DHH, to facilitate code like this: Project.scope.order('created_at DESC').page(current_page).tagged_with(@tag).limit(5).scoping do @topics = @project.topics.scope @todolists = @project.todolists.scope @attachments = @project.attachments.scope @documents = @project.documents.scope end
* | Add `Relation#load`Jon Leighton2012-08-011-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | This method explicitly loads the records and then returns `self`. Rather than deciding between "do I want an array or a relation?", most people are actually asking themselves "do I want to eager load or lazy load?" Therefore, this method provides a way to explicitly eager-load without having to switch from a `Relation` to an array. Example: @posts = Post.where(published: true).load
* | Deprecate :finder_sql, :counter_sql, :insert_sql, :delete_sql.Jon Leighton2012-08-011-0/+11
| |
* | Revert "Remove :finder_sql, :counter_sql, :insert_sql, :delete_sql."Jon Leighton2012-08-011-46/+0
| | | | | | | | | | | | | | | | | | This reverts commit 3803fcce26b837c0117f7d278b83c366dc4ed370. Conflicts: activerecord/CHANGELOG.md It will be deprecated only in 4.0, and removed properly in 4.1.
* | Change AR's CHANGELOG, because it is related to ↵kennyj2012-08-021-1/+1
| | | | | | | | e35c67ae0f920011a2440210041e96659a8de985
* | AR::Relation#order: make new order prepend old oneBogdan Gusiev2012-07-311-0/+9
| | | | | | | | | | | | | | User.order("name asc").order("created_at desc") # SELECT * FROM users ORDER BY created_at desc, name asc This also affects order defined in `default_scope` or any kind of associations.
* | Remove the deprecation of update_column.Rafael Mendonça França2012-07-301-5/+1
| | | | | | | | | | | | update_column was suggested as replacement of update_attribute at the last release of 3-2-stable, so deprecating it now will confuse the users.
* | Revert "Removing composed_of from ActiveRecord."Rafael Mendonça França2012-07-271-23/+0
| | | | | | | | | | | | | | | | | | | | | | This reverts commit 14fc8b34521f8354a17e50cd11fa3f809e423592. Reason: we need to discuss a better path from this removal. Conflicts: activerecord/lib/active_record/reflection.rb activerecord/test/cases/base_test.rb activerecord/test/models/developer.rb
* | Merge pull request #6827 from zephyr-dev/masterJosé Valim2012-07-271-0/+7
|\ \ | | | | | | Validates_presence_of associated object marked for destruction
| * | AR has a subclass of AM:PresenceValidator.Brent Wheeldon & Nick Monje2012-07-201-0/+7
| | | | | | | | | | | | | | | | | | | | | This allows us to mark the parent object as invalid if all associated objects in a presence validated association are marked for destruction. See: https://github.com/rails/rails/issues/6812
* | | Changelog and doc updates for the previous changes.Jon Leighton2012-07-271-3/+21
| | |
* | | Update activerecord/CHANGELOG.mdAyrton De Craene2012-07-261-13/+13
| | | | | | | | | Fixed markdown code indenting
* | | Switched update_column recommendation in changelog to update_columnsPhilip Arndt2012-07-261-1/+1
| | | | | | | | | | | | | | | Related to #7164 Looks like the last one; thanks!
* | | Deprecate update_column in favor of update_columns.Rafael Mendonça França2012-07-241-0/+12
| |/ |/| | | | | Closes #1190
* | Remove :finder_sql, :counter_sql, :insert_sql, :delete_sql.Jon Leighton2012-07-201-0/+10
| |
* | Use attributes instead of table names in migration exampleJosé Valim2012-07-191-1/+1
| |
* | Update changelog for migration generator changeJosé Valim2012-07-181-0/+7
| |
* | 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
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 10:41:34 +0000