| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
Conflicts:
activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb
|
| | |
|
| | |
|
| |
| |
| |
| | |
<pre> block.
|
|\ \
| | |
| | | |
removed warning: shadowing outer local variable
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When calling a query method on an attribute that was not selected by
an ActiveRecord query, an ActiveModel::MissingAttributeError is not
raised. Instead, a nil value is returned, which will return false once
cast to boolean.
This is undesirable, as we should not give the impression that we know
the attribute's boolean value when we haven't loaded the attribute's
(possibly) non-boolean value from the database.
This issue is present on versions going back as far as 2.3, at least.
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| | |
Merged in f41dba27a411fe3e2ddeb8d9ab6856dbb23acd02
[ci skip]
|
|\ \
| | |
| | | |
postgres, map scaled intervals to string datatype
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
* There is no need to delete the primary key from cloned attributes,
since it sets the same pk to nil afterwards.
* Check for empty? instead of any? to run initialize callbacks.
|
| | |
| | |
| | |
| | | |
transaction.
|
| | |
| | |
| | |
| | |
| | | |
Check 0180e090ab6cbe66f7b521a0c03e278a0463accd for more reasoning about
that.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since 810a50dacf9ddddc1d59c1cb350e8ce785c8bf85, the new policy is to
keep old changelogs in their own branches, to avoid manual syncing
across different branches.
Please check that commit for more reasoning about the new policy.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix eagerly loading associations without primary keys
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
|/| |
| | |
| | | |
move validation to AR
|
| | |
| | |
| | |
| | |
| | | |
This will solve the issue that abort the connection transaction when we
skip the tests.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This implements the support to encode/decode JSON
data to/from database and creating columns of type
JSON using a native type [1] supported by PostgreSQL
from version 9.2.
[1] http://www.postgresql.org/docs/9.2/static/datatype-json.html
|
| | | |
|
|\ \ \
| | | |
| | | | |
correct handling of changes in AR::Store, combine multiple store_accessors
|
| | | |
| | | |
| | | |
| | | | |
store_accessor
|
|\ \ \ \
| | | | |
| | | | | |
Fix pluck when columns/tables are reserved words.
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
seamusabshere/use-mysql-binary-for-rake-db-structure-load
Use the 'mysql' binary for 'rake db:structure:load'
|
| |/ / /
| | | |
| | | |
| | | | |
The previous implementation had the strange requirement that db/structure.sql contain only CREATE TABLE sql statements, one per table, separated by double newlines. SQLite3 and PostgreSQL database tasks, on the other hand, simply spawn 'sqlite3' and 'psql' binaries to load the file directly. The new implementation follows this and attempts to respect all current MySQL configuration settings.
|
|\ \ \ \
| | | | |
| | | | | |
Fix for time type columns with invalid time value
|
| | | | | |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
The string_to_dummy_time method was blindly parsing the dummy time string
with Date._parse which returns a hash for the date part regardless
of whether the time part is an invalid time string.
|
|\ \ \ \
| |/ / /
|/| | | |
Modularize postgresql adapter
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | | |
All tests with a custom inheritance_column use the `Vegtable` model.
The field ruby_type on the Company models is no longer needed
|
| | |
| | |
| | |
| | |
| | |
| | | |
previously the tests with and without a custom `inheritance_column`
used the same models. Since the model then has both fields this can lead
to false positives.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I had to create a new table because I needed an STI table,
which does not have both a "type" and a "custom_type"
the test fails with:
1) Error:
test_alt_becomes_works_with_sti(InheritanceTest):
NoMethodError: undefined method `type=' for #<Cabbage id: 1, name: "my cucumber", custom_type: "Cucumber">
/Users/username/Projects/rails/activemodel/lib/active_model/attribute_methods.rb:432:in `method_missing'
/Users/username/Projects/rails/activerecord/lib/active_record/attribute_methods.rb:100:in `method_missing'
/Users/username/Projects/rails/activerecord/lib/active_record/persistence.rb:165:in `becomes'
test/cases/inheritance_test.rb:134:in `test_becomes_works_with_sti'
test/cases/inheritance_test.rb:140:in `test_alt_becomes_works_with_sti'
|
| |
| |
| |
| |
| |
| | |
This is purely a performance optimisation.
See https://gist.github.com/3552829
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is a performance/GC optimisation.
In theory, this could be optimised by the implementation (last time I
checked, this would have no effect on JRuby). But in practise, this make
attribute access faster.
|
| | |
|
| |
| |
| |
| | |
We don't need separate @class_to_pool and @connection_pool hashes.
|
| | |
|
| |
| |
| |
| |
| |
| | |
* Loop rather than recurse in retrieve_connection_pool
* Key the hash by class rather than class name. This avoids creating
unnecessary strings.
|
|\ \
| | |
| | | |
Fix grammar
|
| | | |
|