- 11 11月, 2014 7 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
Just prefer secrets over config
-
由 Rafael Mendonça França 提交于
Allow fallback to LegacyKeyGenerator when secret_key_base is not set but secrets.secret_token is
-
由 Rafael Mendonça França 提交于
Tiny improvement in sqlite3 adapter
-
由 Andrey Deryabin 提交于
- remove unused method `supports_add_column?` - change additional restriction method to `valid_alter_table_type?` - fix code style
-
由 Rafael Mendonça França 提交于
Fix bug found when running individual tests against #17217 after merging
-
由 Rafael Mendonça França 提交于
Fix that a collection proxy could be cached before the save of the owner, resulting in an invalid proxy lacking the owner’s id Conflicts: activerecord/CHANGELOG.md
-
- 10 11月, 2014 9 次提交
-
-
由 Sammy Larbi 提交于
-
由 Yves Senn 提交于
-
由 Godfrey Chan 提交于
We added a deprecation warning for these cases in aa1fadd4, so these are now causing deprecation warnings in the test output. AFAICT, in these two cases, the option is not integral to the purpose of the test, so they can be safely removed
-
由 Godfrey Chan 提交于
Follow up to 212057b9. Since that commit, we need to pass the `route_name` explicitly. This is one of the left-over cases that was not handled in that commit, which was causing `use_route` to be ignored in functional tests.
-
由 Sean Griffin 提交于
Why are people assigning booleans to string columns? >_> We unintentionally changed the behavior on Sqlite3 and PostgreSQL. Boolean values should cast to the database's representation of true and false. This is 't' and 'f' by default, and "1" and "0" on Mysql. The implementation to make the connection adapter specific behavior is hacky at best, and should be re-visted once we decide how we actually want to separate the concerns related to things that should change based on the database adapter. That said, this isn't something I'd expect to change based on my database adapter. We're storing a string, so the way the database represents a boolean should be irrelevant. It also seems strange for us to give booleans special behavior at all in string columns. Why is `to_s` not sufficient? It's inconsistent and confusing. Perhaps we should consider deprecating in the future. Fixes #17571
-
由 Zachary Scott 提交于
Fixed grammar about AS::Notifications [ci skip]
-
由 Rishi Jain 提交于
added description for rails generators, and fixed sentence formation for active_support/notifications [ci skip]
-
由 Aaron Patterson 提交于
Ensure HABTM relationships produce valid class names (Fixes #17119)
-
由 Sammy Larbi 提交于
-
- 09 11月, 2014 6 次提交
-
-
由 Robin Dupret 提交于
[ci skip] Fix typo in command_line.md
-
由 yui-knk 提交于
-
由 Zachary Scott 提交于
[ci skip] Fix comment of SourceAnnotationExtractor#find_in
-
由 Zachary Scott 提交于
-
由 Vijay Dev 提交于
[ci skip] Fix line break on command line guide
-
- 08 11月, 2014 6 次提交
-
-
由 Santiago Pastorino 提交于
default scopes should break the cache on singulur_association.
-
由 Robin Dupret 提交于
Add a section about job testing [ci skip]
-
由 alfa-jpn 提交于
fixes #17495
-
由 yui-knk 提交于
-
由 Aaron Patterson 提交于
Delegate comparison operator to value
-
由 Aaron Patterson 提交于
if you specify a default scope on a model, it will break caching. We cannot predict what will happen inside the scope, so play it safe for now. fixes #17495
-
- 07 11月, 2014 12 次提交
-
-
由 Yves Senn 提交于
Guides: Corrected name for assigns key [ci skip]
-
由 Jimmy Petersen 提交于
- Integration test example is now using 'articles' name for both path and assigns key.
-
由 Yves Senn 提交于
-
由 Yves Senn 提交于
-
由 Yves Senn 提交于
-
由 Yves Senn 提交于
-
由 Zachary Scott 提交于
[ci skip] modify default host in command line guide
-
由 yuuji.yaginuma 提交于
-
由 Yves Senn 提交于
Print out a meaningful error when ActiveRecord::ReadOnlyRecord is raised
-
由 Franky W 提交于
Currently, there is no messages which get printed out. Convoluted system may have hooks that create other objects in which case we only fail with no messages. This commit changes this information allowing you to know which object is the one that actually raised the error.
-
由 Rafael Mendonça França 提交于
[Enh] Made the ActiveModel::Dirty#clear_attribute_changes method public
-
由 Daniele Di Bernardo 提交于
In Rails 4.2 it is impossible to define a custom default value for a model's attribute without making it appear as _changed?, especially when the model is first initialized. Making this method publicly visible will allow such a behaviour, without the need to use private APIs.
-