- 29 3月, 2016 2 次提交
-
-
由 Vipul A M 提交于
Fix typo in headers comment [ci skip]
-
由 Grey Baker 提交于
-
- 28 3月, 2016 5 次提交
-
-
由 Vipul A M 提交于
Update how to clear the association cache
-
由 Sammy Larbi 提交于
Passing `true` to the association has been deprecated.
-
由 प्रथमेश Sonpatki 提交于
Update `numericality` validation docs
-
由 Arkadiusz Fal 提交于
Add `:other_than` option documentation.
-
由 Kasper Timm Hansen 提交于
show correct command name in help of rails runner
-
- 27 3月, 2016 10 次提交
-
-
由 Vipul A M 提交于
[ci skip] relations inside <tt> tag
-
由 Sourav Moitra 提交于
s removed objects added
-
由 Vipul A M 提交于
Fix description for method ActiveRecord::ConnectionAdapters::SchemaStatements#add_timestamps [ci skip]
-
由 Bogdan 提交于
Fix description for method ActiveRecord::ConnectionAdapters::SchemaStatements#add_timestamps [ci skip]
-
由 Arun Agrawal 提交于
remove old-dead link
-
由 Mohamad Abras 提交于
-
由 Jon Moss 提交于
add `:index_errors` option to example [ci skip]
-
由 yuuji.yaginuma 提交于
-
由 Kasper Timm Hansen 提交于
`skip` raises an exception to abort the execution of the test, so `super` would never be called and thus `@rx_adapter` and `@tx_adapter` would never have been defined at the time of teardown. Define them just before skipping and zap the warnings.
-
由 Kasper Timm Hansen 提交于
EM::Hiredis were spewing screenfuls of warnings when running the Action Cable tests. Copied over the technique that shushes up faye-websocket in the client tests, so we can reduce the noise ratio. Note: there's still warnings spewed after tests have finished when EM::Hiredis shuts down. I haven't been able to shush them up yet.
-
- 26 3月, 2016 6 次提交
-
-
由 yuuji.yaginuma 提交于
If use rails together with `spring`, `spring` is rewrite `$0` in the interior command name. Therefore, for `$0` correct command name does not appear, `$0` has been modified so that it does not use.
-
由 प्रथमेश Sonpatki 提交于
Highlight the dynamic method finder 'find_by_' [ci skip]
-
由 Santosh Wadghule 提交于
-
由 Matthew Draper 提交于
development.rb file always exists so we don't need a check for it
-
由 Prathamesh Sonpatki 提交于
-
由 Vipul A M 提交于
Correct typos in "Active Record Query Interface" guide
-
- 25 3月, 2016 15 次提交
-
-
由 Laura Murphy-Clarkin 提交于
-
由 Kasper Timm Hansen 提交于
Do not create a hash key when calling ActiveModel::Errors#include?
-
由 Kasper Timm Hansen 提交于
set in no more used in ActionView::Template::Types
-
由 Kasper Timm Hansen 提交于
Fix typo in Action Pack changelog [ci skip]
-
由 Gaurav Sharma 提交于
initially set is used for template type https://github.com/rails/rails/commit/67f55e28 after this commit https://github.com/rails/rails/commit/91f2ad36 it’s not require
-
由 Prathamesh Sonpatki 提交于
-
由 Rafael Mendonça França 提交于
This reverts commit 43ccebc1. This is not fixing the configuration problem since we are assigning to the ActiveRecord::Base not the configuration. See #24303.
-
由 Sean Griffin 提交于
Since precision is always larger than scale, it can actually change rounding behavior. Given a precision of 5 and a scale of 3, when you apply the precision of 5 to `1.25047`, the result is `1.2505`, which when the scale is applied would be `1.251` instead of the expected `1.250`. This issue appears to only occur with floats, as scale doesn't apply to other numeric types, and the bigdecimal constructor actually ignores precision entirely when working with strings. There's no way we could handle this for the "unknown object which responds to `to_d`" case, as we can't assume an interface for applying the scale. Fixes #24235
-
由 Arthur Nogueira Neves 提交于
Move sequence value methods to Model level
-
由 Sean Griffin 提交于
When a proc is given as a default value, the form builder ends up displaying `Proc#to_s` when the default is used. That's because we didn't handle the proc until type casting. This issue technically can occur any time that a proc is the value before type casting, but in reality the only place that will occur is when a proc default is provided through the attributes API, so the best place to handle this edge case is there. I've opted to memoize instead of just moving the `Proc#call` up, as this made me realize that it could potentially interact very poorly with dirty checking. The code here is a little redundant, but I don't want to rely on how `value_before_type_cast` is implemented in the super class, even if it's just an `attr_reader`. Fixes #24249 Close #24306
-
由 Esteban Pastorino 提交于
From: https://github.com/rails/rails/issues/24279 Problem: By doing `record.errors.include? :foo`, it adds a new key to the @messages hash that defaults to an empty array. This happens because of a combination of these 2 commits: https://github.com/rails/rails/commit/b97035df64f5b2f912425c4a7fcb6e6bb3ddab8d (Added in Rails 4.1) and https://github.com/rails/rails/commit/6ec8ba16d85d5feaccb993c9756c1edcbbf0ba13#diff-fdcf8b65b5fb954372c6fe1ddf284c78R76 (Rails 5.0) By adding the default proc that returns an array for non-existing keys, ruby adds that key to the hash. Solution: Change `#include?` to check with `has_key?` and then check if that value is `present?`. Add test case for ActiveModels::Errors#include?
-
由 Arthur Nogueira Neves 提交于
Make 'migrate' clear the schema cache afterward
-
由 Arthur Neves 提交于
`prefetch_primary_key?` and `next_sequence_value` methods live in the connection level at the moment, that make sense when you are generating the sequence from the database, in the same connection. Which is the use case today at the Oracle and Postgres adapters. However if you have an service that generates IDs, that has nothing to do with the database connection, and should not be fetched from there. Another use case, is if you want to use another connection to fetch IDs, that would not be possible with the current implementation, however when we move those methods to the model level, you can use a new connection there. Also this makes easier for gems to add behavior on those methods.
-
由 Jeremy Daer 提交于
-
由 Chris Arcand 提交于
Without clearing the caches afterward, removals done in migrations would not be reflected in a separate task in the same process. That is, given a table with a migration to remove a column, the schema cache would still reflect that a table has that in something such as the 'db:seed' task: `rake db:migrate db:seed` (A common thing to do in a script for a project ala `bin/setup`) vs `rake db:migrate && rake db:seed` (Two processes) The first would not reflect that the column was removed. The second would (cache reset).
-
- 24 3月, 2016 2 次提交
-
-
由 Rafael França 提交于
Fix a tip in Active Record time attributes deprecation
-
由 Rafael França 提交于
Use Range#cover? for Date inclusion validator
-