- 10 12月, 2014 7 次提交
-
-
由 Zachary Scott 提交于
[ci skip] fix typo in MessageVerifier#verify docs
-
由 yuuji.yaginuma 提交于
-
由 Zachary Scott 提交于
Adding information about 'allow_nil' option for 'numericality' [ci skip]
-
由 Andrey Nering 提交于
-
由 Rafael Mendonça França 提交于
Add guides for `required` model generator option
-
由 Carlos Souza 提交于
Related to this PR #16062 [ci skip]
-
由 Richard Schneeman 提交于
Testing Guides: adding TIP about database permission problems [ci skip]
-
- 09 12月, 2014 20 次提交
-
-
由 andrey.nering@gmail.com 提交于
loading fixtures to the database. Reference #17542
-
由 Rafael Mendonça França 提交于
Fix options overwritten by super
-
由 Jose Añasco 提交于
-
由 Akira Matsuda 提交于
-
由 Carlos Antonio da Silva 提交于
Remove unused "Developer" fixtures from tests
-
由 Rafael Mendonça França 提交于
[ci skip] Fix typo
-
由 yui-knk 提交于
-
由 Sean Griffin 提交于
The test added in 42418cfc wasn't actually testing anything, since the bug was with TZ aware attributes only.
-
由 Sean Griffin 提交于
PostgreSQL for example, allows infinity as a valid value for date time columns. The PG type has explicit handling for that case. However, time zone conversion will end up trampling that handling. Unfortunately, we can't call super and then convert time zones. However, if we get back nil from `.in_time_zone`, it's something we didn't expect so we can let the superclass handle it. Fixes #17971
-
由 claudiob 提交于
The `RecursiveCallbackDeveloper` and `ImmutableMethodDeveloper` classes are not used anymore in tests, and neither is the `@Cancelled` variable.
-
由 Sean Griffin 提交于
`freeze` will ultimately end up freezing the `AttributeSet`, which in turn freezes its `@attributes` hash. However, we actually insert a special object to lazily instantiate the values of the hash on demand. When it does need to actually instantiate all of them for iteration (the only case is `ActiveRecord::Base#attributes`, which calls `AttributeSet#to_h`), it will set an instance variable as a performance optimization Since it's just an optimization for subsequent calls, and that method being called at all is a very uncommon case, we can just leave the ivar alone if we're frozen, as opposed to coming up with some overly complicated mechanism for freezing which allows us to continue to modify ourselves. Fixes #17960
-
由 Sean Griffin 提交于
The user is able to pass PG string literals in 4.1, and have it converted to an array. This is also possible in 4.2, but it would remain in string form until saving and reloading, which breaks our `attr = save.reload.attr` contract. I think we should deprecate this in 5.0, and only allow array input from user sources. However, this currently constitutes a breaking change to public API that did not go through a deprecation cycle.
-
由 Rafael Mendonça França 提交于
Also avoid using try since is_a? is faster for this case.
-
由 Rafael Mendonça França 提交于
Make error message clearer that :on requires a symbol, not a string
-
由 Rafael Mendonça França 提交于
fixing mailer previews for apps with globbing route
-
由 Rafael Mendonça França 提交于
add brackets around attribute_name [ci skip]
-
由 _tiii 提交于
since 'attr_name_will_change!' is not an actual method it should be clearer that you have to insert the attribute name as in line 104 [ci skip]
-
由 Zachary Scott 提交于
-
由 Zachary Scott 提交于
Add note to Store about uniqueness validation (#17954) [skip ci]
-
由 Rafael Mendonça França 提交于
Test coverage for ActiveJob generator
-
- 08 12月, 2014 6 次提交
-
-
由 Mike Chau 提交于
-
由 Richard Schneeman 提交于
minor sentences fixes
-
由 Carol Nichols 提交于
The validation added in 5a3dc809 will reject values for the `:on` option for after_commit and after_rollback callbacks that are string values like `"create"`. However, the error message says ":on conditions for after_commit and after_rollback callbacks have to be one of create,destroy,update". That looks like a string value *would* be valid. This commit changes the error message to say ":on conditions for after_commit and after_rollback callbacks have to be one of [:create, :destroy, :update]", making it clearer that symbols are required.
-
由 Neeraj Singh 提交于
-
由 Zachary Scott 提交于
Fix grammar of sentence in Reflection documentation [ci skip]
-
由 eileencodes 提交于
-
- 07 12月, 2014 3 次提交
-
-
由 Richard Schneeman 提交于
[ci skip] add `enable_extension` to PostgreSQL hstore example
-
由 Kir Shatrov 提交于
-
由 yuuji.yaginuma 提交于
-
- 06 12月, 2014 4 次提交
-
-
由 Santiago Pastorino 提交于
Mounted Rack apps should have default named routes based on app name
-
由 Richard Schneeman 提交于
[ci skip] update rails version to 3.2.21
-
由 Richard Schneeman 提交于
Add Guides note to change cache namespace
-
由 T.J. Schuck 提交于
This fixes a regression in 4.2.0 from 4.1.8. https://github.com/rails/rails/pull/17823 fixed a similar regression regarding _explicitly_ named routes for a mounted Rack app, but there was another regression for the default value. With a route like: Rails.application.routes.draw do mount Mountable::Web, at: 'some_route' end The "Prefix" column of rake routes gives the following: - 4.1.8: mountable_web - 4.2.0.beta1-4: [nothing] - 4.2.0.rc1: [nothing] - 4.2.0.rc2: some_route <- regression This fixes the default to go back to being based off the name of the class like the docs specify: https://github.com/rails/rails/blob/785d04e3109f69d0b9b9f4732179592f0ef04e52/actionpack/lib/action_dispatch/routing/mapper.rb#L558-L560 Explicitly named routes still work correctly per https://github.com/rails/rails/pull/17823: Rails.application.routes.draw do mount Mountable::Web, at: 'some_route', as: 'named' end - 4.1.8: named - 4.2.0.beta1-4: [nothing] - 4.2.0.rc1: [nothing] - 4.2.0.rc2: named
-