- 08 7月, 2014 8 次提交
-
-
由 Rafael Mendonça França 提交于
Warm up cache to prevent assertion failure.
-
由 Zuhao Wan 提交于
-
由 Rafael Mendonça França 提交于
Remove PG's definition of `type_cast`
-
由 Rafael Mendonça França 提交于
Don't rely on the sql type to quote XML columns in PG
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
It always responds to mounted_helpers now
-
由 Aaron Patterson 提交于
-
由 Rafael Mendonça França 提交于
Avoid retrieving connection in ActiveRecord::QueryCache multiple times.
-
- 07 7月, 2014 13 次提交
-
-
由 Rafael Mendonça França 提交于
Remove the `text?` predicate from the type objects
-
由 Eileen M. Uchitelle 提交于
Add callbacks documentation for upgrading to 4.1.
-
由 Nick Pellant 提交于
The previous code example for the new explicit block requirement when setting callbacks was a little confusing. This commit makes the example more obvious.
-
由 Robin Dupret 提交于
As discussed in #15304, we need to automate this process but for now, having out-of-date versions is not ideal. Since master targets 4.2.0, let's also update references to the last 4.1 version to 4.2.0. Finally, let's remove mentions to versions when this is not needed. The guides cover the features of the current version anyway. [Juanito Fatas + Robin Dupret]
-
由 Nick Pellant 提交于
It is now expected in 4.1 to use an explicit block rather than implicit when setting callbacks through ActiveSupport::Callbacks. This commit highlights this new expectation as part of the upgrading documentation.
-
由 Guo Xiang Tan 提交于
-
由 Sean Griffin 提交于
Fix ActiveSupport::Callbacks #set_callback docs.
-
由 Nick Pellant 提交于
A minor version breakage due to a rewrite of the callbacks code now requires an explicit block to be passed to #set_callback. This amends the documentation.
-
由 Sean Griffin 提交于
This was only used for uniqueness validations. The first usage was in conjunction with `limit`. Types which cast to string, but are not considered text cannot have a limit. The second case was only with an explicit `:case_sensitive => true` option given by the user.
-
由 Sean Griffin 提交于
-
由 Sean Griffin 提交于
All cases except for `nil` in an array have been removed. `nil` in an array is handled by the Array type object.
-
由 Zachary Scott 提交于
adapter, fixed from #16057 [ci skip]
-
由 Zachary Scott 提交于
[ci skip] /sqlite/i --> SQLite
-
- 06 7月, 2014 16 次提交
-
-
由 Robin Dupret 提交于
[ci skip] add guide for ActiveModel::Naming
-
由 Akshay Vishnoi 提交于
-
由 Seb Jacobs 提交于
Prior to this commit shallow resources would only generate paths for non-direct children (with a nested depth greater than 1). Take the following routes file. resources :blogs do resources :posts, shallow: true do resources :comments do resources :tags end end end This would generate shallow paths for `tags` nested under `posts`, e.g `/posts/:id/tags/`, however it would not generate shallow paths for `comments` nested under `posts`, e.g `/posts/:id/comments/new`. This commit changes the behaviour of the route mapper so that it generate paths for direct children of shallow resources, for example if you take the previous routes file, this will now generate shallow paths for `comments` nested under `posts`, .e.g `posts/:id/comments/new`. This was the behaviour in Rails `4.0.4` however this was broken in @jcoglan's fix for another routes related issue[1]. This also fixes an issue[2] reported by @smdern. [1] https://github.com/rails/rails/commit/d0e5963 [2] https://github.com/rails/rails/issues/15783
-
由 Matthew Draper 提交于
active_record: Type cast booleans and durations for string columns.
-
由 Dylan Thacker-Smith 提交于
-
由 Zachary Scott 提交于
[ci skip] link directly to ActionMailer Previews documentation
-
由 Zachary Scott 提交于
[ci skip] Concludes changelog links in the bottom.
-
由 Juanito Fatas 提交于
This way when we do next release notes, this would be easier to copy and change.
-
由 Godfrey Chan 提交于
This reverts commit a0309775. This needs more work before it would work correctly on master.
-
由 Godfrey Chan 提交于
Fixed issue with ActiveRecord serialize object as JSON Conflicts: activerecord/CHANGELOG.md activerecord/lib/active_record/attribute_methods/serialization.rb
-
由 Matthew Draper 提交于
If our connection is explicitly non-strict, tell MySQL
-
由 Godfrey Chan 提交于
One of the author fixture we have ("david") references an author address by ID. Since we disable FK checks when inserting fixtures, this is all fine until we try to update it, at which point MySQL would complain about the missing row referenced by the `author_address_id`. [Godfrey Chan, Matthew Draper]
-
由 Matthew Draper 提交于
We default to making the connection strict, but have historically relied on the MySQL default when we want it to be non-strict. On some (recent?) versions of MySQL, new connections default to being strict, so if we've been told 'strict:false', we're obliged to pass that on. This fixes a test failure that we've seen turn up on relatively-new development machines, so we do already have a test covering it.
-
由 Godfrey Chan 提交于
This reverts commit e84799d9, e31104c1 and e6ca8e2c
-
由 Rafael Mendonça França 提交于
Use the type object for quoting PG Ranges
-
由 Aditya Kapoor 提交于
-
- 05 7月, 2014 3 次提交
-
-
由 Sean Griffin 提交于
-
由 Sean Griffin 提交于
-
由 Sean Griffin 提交于
Removed mentions of non-existent methods, also added a mention for `Date.current`, which is analagous to `Time.current`. Closes #16061.
-