| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Remove useless `test_supports_primary_key`
|
| |
| |
| |
| |
| | |
`supports_primary_key?` method is defined in `AbstractAdapter` so does
not raise any errors.
|
|/ |
|
|\
| |
| | |
Simplify the regex for `unsigned?` method
|
| |
| |
| |
| |
| | |
It is enough to distinguish only the trailing `unsigned` and
`unsigned zerofill`.
|
|\ \
| | |
| | | |
Throw friendly error message when fixture is not a hash
|
| | |
| | |
| | |
| | |
| | |
| | | |
Right now, when fixture is not a Hash we throw an error message
saying "fixture is not a hash". This is not very user friendly because
it's not saying which fixture is invalid.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
make sql statements frozen
dup if arel is not our string
expect runtime error
dont wrap runtime error in invalid
log errors will now be treated as runtime errors
update changelog
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes the following warning.
```
test/caching_test.rb:986: warning: parentheses after method name is interpreted as
test/caching_test.rb:986: warning: an argument list, not a decomposed argument
test/cases/adapters/mysql2/reserved_word_test.rb:146: warning: parentheses after method name is interpreted as
test/cases/adapters/mysql2/reserved_word_test.rb:146: warning: an argument list, not a decomposed argument
```
Ref: https://github.com/ruby/ruby/commit/65e27c8b138d6959608658ffce2fa761842b8d24
|
|\ \ \
| | | |
| | | | |
Schema cache in YAML
|
| | | | |
|
| |_|/
|/| | |
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
kamipo/prevent_range_error_for_belongs_to_associations
Prevent `RangeError` for `belongs_to` associations
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently to access `belongs_to` associations raises a `RangeError` if
foreign key attribute has out of range value.
It should return a nil value rather than raising a `RangeError`.
Fixes #20140.
|
|\ \ \
| | | |
| | | | |
Translate numeric value out of range to the specific exception
|
| | | |
| | | |
| | | |
| | | | |
Raise `ActiveRecord::RangeError` when values that executed are out of range.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Race conditions can occur when an ActiveRecord is destroyed
twice or destroyed and updated. The callbacks should only be
triggered once, similar to a SQL database trigger.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Moved database-specific ActiveModel types into ActiveRecord
|
| | | | |
| | | | |
| | | | |
| | | | | |
ie. DecimalWithoutScale, Text and UnsignedInteger
|
| | | | |
| | | | |
| | | | |
| | | | | |
- If aliased, then use the aliased attribute name.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- If aliased, then use the aliased attribute name.
- Fixes #26417.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Fix association scope inside autosaved association callbacks
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Raise `ActiveRecord::NotNullViolation` when a record cannot be inserted
or updated because it would violate a not null constraint.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix `add_index` to normalize column names and options
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently does not work the following code.
```ruby
add_index(:people, ["last_name", "first_name"], order: { last_name: :desc, first_name: :asc })
```
Normalize column names and options to fix the issue.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Make `:auto_increment` option works on `:bigint`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Follow up to #27272.
|
| | | | | | | |
|
|/ / / / / / |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Using `:auto_increment` option for abstracting the DB-specific auto
incremental types. It is worth to ease to implement the compatibility
layer.
|
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
While working on updating Paper Trail for 5.1 compatibility, I noticed
that I was required to pass a second argument to `attribute`. I didn't
intend for this to be the case, as `attribute :foo` is totally
reasonable shorthand for "I want `attr_accessor :foo`, but also have it
work with things like `.attributes` and `ActiveRecord::Dirty`"
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix that unsigned with zerofill is treated as signed
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #27125.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
use public Module#include instead of send :include
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Follow up to #18767
|
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
sergey-alekseev/uniqueness-validation-scope-with-polymorphic-association
fix the uniqueness validation scope with a polymorphic association
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
https://gist.github.com/sergey-alekseev/946657ebdb5e58d1bee115714056ec96
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If it's enabled globally, it's on regardless of how individual threads
are set.
|
|/ / / / / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I assume it's upset because of the change in d314646c965b045724e6bdb9d61dcecfabc0ba8f,
but I don't yet understand why.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Follow up to #25395.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Suppress migration message in the test
|
| | | | | | |
|