| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
kamipo/append_sql_mode_instead_of_overwriting_in_strict_mode
Append sql_mode instead of overwriting in strict mode
|
| |
| |
| |
| | |
For keep the default SQL mode.
|
| |
| |
| |
| |
| |
| |
| |
| | |
[ci skip]
Sync AV, AR, AJ, AS, AM changelogs with our 5.0 release notes draft.
This is a follow up to c94045d and contains changes made since the
release of beta1.
|
|\ \
| | |
| | |
| | |
| | | |
RochesterinNYC/better-error-message-for-includes-relations-missing
Improve error message for missing relations for includes and eager_load
|
| | |
| | |
| | |
| | | |
relations
|
|\ \ \
| | | |
| | | | |
Creates development and test databases in db:migrate task
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts a334425caff9b2140d5e99fcfc2eb8c4ab10bdfa.
The main reason is that now the workflow is inconsistent when using
spring.
When using spring `RAILS_ENV` is always set, so only one database is
created.
This means that in development `bin/rake db:create` and `bundle exec
rake db:create` have different results.
It also breaks the `bin/setup` script since `bin/rake db:setup
db:test:prepare` will fail.
|
|/ / /
| | |
| | |
| | |
| | | |
In this patch, all log-related stuff in `ActiveSupport::Dependencies`
is removed because the logging is no longer useful.
|
| | |
| | |
| | |
| | | |
We should use #find_or_initialize_by and #find_or_create_by because #first_or_initialize and #first_or_create methods are not the public API
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
```
$ ARCONN=mysql2 be ruby -w -Itest test/cases/scoping/default_scoping_test.rb
Using mysql2
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: method redefined; discarding old female
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: previous definition of female was here
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: method redefined; discarding old male
/Users/kamipo/src/github.com/rails/rails/activerecord/lib/active_record/scoping/named.rb:158: warning: previous definition of male was here
```
|
|\ \
| | |
| | |
| | |
| | | |
kamipo/case_sensitive_comparison_for_non_string_column
The BINARY Operator is only needed for string columns
|
| | |
| | |
| | |
| | | |
Follow up to #13040.
|
| | |
| | |
| | |
| | | |
I'm unsure how this passed CI in the pull request.
|
|\ \ \
| | | |
| | | | |
Extract `default_primary_key?` to refactor `column_spec_for_primary_key`
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Dump `bigint` instead of `integer` with `limit: 8` for schema dumper
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Before:
```ruby
create_table "big_numbers", force: :cascade do |t|
t.integer "bigint_column", limit: 8
end
```
After:
```ruby
create_table "big_numbers", force: :cascade do |t|
t.bigint "bigint_column"
end
```
|
|\ \ \ \
| |/ / /
|/| | | |
Passing `table_name` to `Column#initialize` to avoid `instance_variable_set`
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
working
Currently the results of `column.serial?` is not correct. For
`column.serial?` correctly working, initialize `column.table_name`
immediately.
|
|\ \ \ \
| | | | |
| | | | | |
Fix bigserial appears with limit 8 for schema dumper
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Before:
```ruby
create_table "postgresql_big_serials", force: :cascade do |t|
t.bigserial "seq", limit: 8, null: false
end
```
After:
```ruby
create_table "postgresql_big_serials", force: :cascade do |t|
t.bigserial "seq", null: false
end
```
|
| | | | |
| | | | |
| | | | | |
The comments of add_foreign_key method was displaying incorrect constraint name.
|
| | | | |
| | | | |
| | | | |
| | | | | |
References https://github.com/rails/homepage/issues/46.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Follow up to #24079
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Execute default_scope defined by abstract class within the scope of subclass
|
| | |/ / /
| |/| | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Remove outdated comment [ci skip]
|
| |/ / /
| | | |
| | | |
| | | | |
Currently column options handled by the type map in Rails 4.2.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
related to #19324 and #18606
[skip ci]
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fixes funny spelling in an AR test
|
| | | | |
| | | | |
| | | | |
| | | | | |
- marked_for_destroyal -> marked_for_destruction
|
|\ \ \ \ \
| | | | | |
| | | | | | |
No need to extract a limit for a boolean type
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Conflicts:
guides/source/association_basics.md
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
As shown below, we should use <tt>...</tt> for string literal
```
$ echo "+'id'+" | rdoc --pipe
<p>+'id'+</p>
$ echo "<tt>'id'</tt>" | rdoc --pipe
<p><code>'id'</code></p>
```
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[ci skip]
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Follow up to #22543.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
chage `date_time` type ` to `datetime`
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Since we are using `datetime` in migration, better to use `datetime` is I think that confusion is less.
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
There is a need to pass the keyword arguments to `attribute` method.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Currently use minitest mock, mocha is not used.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Introduce a predicate method that doesn't need to build a scope chain,
but also hides the data structure used for representing the scope chain.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We know a reflection can be considered as `nested?` if the source
reflection or the through reflection are also through reflections (since
the through reflection will also add another join table). This allows
us to avoid traversing the entire reflection tree just to calculate whether or
not there will be more join tables.
|
| |_|_|/ / /
|/| | | | | |
|