| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
option
Backports #5900
Conflicts:
activerecord/lib/active_record/connection_adapters/abstract_mysql_adapter.rb
activerecord/test/cases/adapters/mysql/mysql_adapter_test.rb
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit 1166d49f62ccab789be208112163ad13183224e2.
Conflicts:
activerecord/test/cases/associations/eager_test.rb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The #relation method gets called in four places and the return value was instantly cloned in three of them. The only place that did not clone was ActiveRecord::Scoping::Default::ClassMethods#unscoped. This introduced a bug described in #5667 and should really clone the relation, too. This means all four places would clone the relation, so it doesn't make a lot of sense caching it in the first place.
The four places with calls to relations are:
activerecord/lib/active_record/scoping/default.rb:110:in `block in build_default_scope'"
activerecord/lib/active_record/scoping/default.rb:42:in `unscoped'"
activerecord/lib/active_record/scoping/named.rb:38:in `scoped'"
activerecord/lib/active_record/scoping/named.rb:52:in `scope_attributes'"
Conflicts:
activerecord/lib/active_record/core.rb
|
|
|
|
|
|
|
|
| |
Causes a subtle regression where record.reload includes the default
scope. Hard to reproduce in isolation. Seems like the relation is
getting infected by some previous usage.
This reverts commit dffbb521a0d00c8673a3ad6e0e8ff526f32daf4e.
|
| |
|
|\
| |
| | |
Remove unused castcode
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Fixing Identity Map when using find select in rails 3.2
|
| |
| |
| |
| |
| |
| |
| |
| | |
the code harder to read. Minor changes to contain_all_columns in IdentityMap.
Conflicts:
activerecord/lib/active_record/base.rb
|
| |
| |
| |
| | |
it's more readable
|
| |
| |
| |
| | |
the columns, so we don't get 'MissingAttributeError' later when trying to access other fields of the same record.
|
|\ \ |
|
| | | |
|
| | | |
|
| |/
|/|
| |
| |
| |
| | |
Conflicts:
activerecord/test/cases/associations/eager_test.rb
|
| | |
|
| |
| |
| |
| | |
Fix indenting in migration generator
|
|\ \
| |/
|/| |
force datetime attributes to be changed
|
| |
| |
| |
| | |
backport ddb5d2f756d9d2655a07791a3b62832efd588474 to 3-2-stable
|
| | |
|
|/
|
|
| |
Issue with schema dump
|
|\
| |
| | |
[3-2-stable] migrate(:down) method with table_name_prefix
|
| | |
|
| |
| |
| |
| | |
generating migration'
|
|/ |
|
| |
|
|
|
|
| |
Fix GH #5430. A Payload name for schema_search_path should be SCHEMA.
|
|
|
|
| |
variables' in mutex ConditionVariables
|
|
|
|
| |
ActiveRecord::Base::ConnectionSpecification objects.
|
|
|
|
|
|
| |
add test to show offset query_methods on mysql & mysql2
change test to cover public API
|
| |
|
|\
| |
| | |
ConnectionPooll#clear_active_connections! rdoc inaccuracy since 3.2.0
|
| |
| |
| |
| | |
threads, it doesn't since 3.2.0
|
|/ |
|
|
|
|
|
|
|
|
|
| |
(cherry picked from commit 5282485d310d1a6ffcf55e4e7f56ab234e16880d)
Conflicts:
activerecord/CHANGELOG.md
activerecord/lib/active_record/dynamic_finder_match.rb
|
| |
|
|
|
|
| |
use for the current thread. fixes #5330
|
| |
|
|
|
|
| |
Update ActiveRecord::AttributeMethods#attribute_present? to return false for empty strings
|
|
|
|
| |
builder
|
|
|
|
| |
Change the default for newly generated applications to whitelist all attribute assignment. Also update the generated model classes so users are reminded of the importance of attr_accessible.
|
|
|
|
|
|
| |
would get ConnectionNotEstablished error because it always tried to use
ActiveRecord::Base's connection, even though it should be using the connection
of the model whose context we're operating in
|
|
|
|
|
|
| |
Conflicts:
activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 3dbedd2 added NOT NULL constraints both to table
creation and modification. For creation the new default
makes sense, but the generic situation for changing a
table is that there exist records. Those records have
no creation or modification timestamps, and in the
general case you don't even know them, so when updating
a table these constraints are not going to work. See
a bug report for this use case in #3334.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 3-2-2:
bumping to 3.2.2
Ensure [] respects the status of the buffer.
Merge pull request #4834 from sskirby/fix_usage_of_psql_in_db_test_prepare
Merge pull request #5084 from johndouthat/patch-1
updating RAILS_VERSION
delete vulnerable AS::SafeBuffer#[]
use AS::SafeBuffer#clone_empty for flushing the output_buffer
add AS::SafeBuffer#clone_empty
fix output safety issue with select options
|
| | |
|
| |
| |
| |
| | |
Fix usage of psql in db:test:prepare
|