| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit fixes the build but we need to further investigate the root cause,
to see if it can be fixed.
The test fails under `MysqlAdapter` with:
```
ActiveRecord::UnknownAttributeError: unknown attribute: なまえ
```
The root cause is that the returned column names from the adapter
have the wrong encoding:
```ruby
columns = Weird.columns_hash.keys
columns # => ["id", "a$b", "\xE3\x81\xAA\xE3\x81\xBE\xE3\x81\x88", "from"]
columns.map(&:encoding) # => [#<Encoding:ASCII-8BIT>, #<Encoding:ASCII-8BIT>, #<Encoding:ASCII-8BIT>, #<Encoding:ASCII-8BIT>]
columns.map {|c| c.dup.force_encoding "utf-8"} # => ["id", "a$b", "なまえ", "from"]
```
From what I can tell the MySQL variables are fine:
```
ActiveRecord::Base.connection.execute("show variables")
...
character_set_client utf8
character_set_connection utf8
character_set_database utf8
character_set_filesystem binary
character_set_results utf8
character_set_server utf8
character_set_system utf8
character_sets_dir /usr/local/Cellar/mysql/5.5.29/share/mysql/charsets/
collation_connection utf8_general_ci
collation_database utf8_unicode_ci
collation_server utf8_general_ci
...
```
|
|
|
|
| |
Closes #11062
|
| |
|
| |
|
|
|
|
| |
Fix in-memory tests
|
| |
|
|\
| |
| | |
Load fixtures from linked folders[master]
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the `db/` directory is not present on a remote machine it will blow up in unexpected ways with error messages that do not indicate there is a missing directory:
```
SQLite3::CantOpenException: unable to open database file
```
This PR checks to see if a directory exists for the sqlite3 file and if not creates it for you.
This PR is an alternative to #11692 as suggested by @josevalim
|
|\ \
| | |
| | | |
Changing the def self.table_name to self.table_name in the column_name.r...
|
| | | |
|
|/ / |
|
|/ |
|
|\
| |
| | |
Define enable_extension method to prevent undefined method error
|
| |
| |
| |
| |
| |
| |
| | |
When mixing postgresql and another adapter like sqlite3 (for dev and test
respectively), the task `db:test:prepare` will fail due to the `enable_extension`
method not being defined in the abstract adapter. This patch simply adds an
empty definition to prevent it.
|
| | |
|
| |
| |
| |
| | |
Closes: #11706
|
| |
| |
| |
| |
| | |
tesetcases assertion to case insensitive because Oracle database adapter
handles table name in uppercase.
|
| |
| |
| |
| |
| | |
decouple the builder classes from the model. Builder objects should be
easier to reuse now.
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Make test order independent
|
| | |
| | |
| | |
| | |
| | | |
postgresql test if randomly executed then executes "SHOW max_identifier_length". Hence
the need to ignore certain predefined sqls that deal with system calls.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
activerecord/CHANGELOG.md
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
order on the old ones
The previous behavior added a major backward incompatibility since it
impossible to have a upgrade path without major changes on the
application code.
We are taking the most conservative path to be consistent with the idea
of having a smoother upgrade on Rails 4.
We are reverting the behavior for what was in Rails 3.x and,
if needed, we will implement a new API to prepend the order clauses in
Rails 4.1.
|
|\ \ \
| |/ /
|/| | |
Add ability to specify how a class is converted to Arel predicate when passed to where
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds the ability for rails apps or gems to have granular control
over how a domain object is converted to sql. One simple use case would
be to add support for Regexp. Another simple case would be something
like the following:
class DateRange < Struct.new(:start, :end)
def include?(date)
(start..end).cover?(date)
end
end
class DateRangePredicate
def call(attribute, range)
attribute.in(range.start..range.end)
end
end
ActiveRecord::PredicateBuilder.register_handler(DateRange,
DateRangePredicate.new)
More complex cases might include taking a currency object and converting
it from EUR to USD before performing the query.
By moving the existing handlers to this format, we were also able to
nicely refactor a rather nasty method in PredicateBuilder.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
neerajdotname/log_should_mimick_original_log_method
interceptor should mimick original method
|
| |/ /
| | |
| | |
| | | |
This fix also makes the test order independent.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
neerajdotname/use_method_with_active_record_default_timezone
use method with_active_record_default_timezone
|
| |/ / |
|
|/ /
| |
| |
| | |
This method is already present in helper.rb
|
| |
| |
| |
| |
| |
| | |
This reverts commit 10259c3e906da2191ef0d43cd664a3b5504d9f8c.
reason: this causes rake test_mysql and test_mysql2 fail
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Cleanup of class_name
|
| | |
| | |
| | |
| | | |
Don't think class name is needed as by default belongs_to :select will be linked to Select class.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
neerajdotname/fix_order_dependent_test_for_migration
fix order dependent test related to migration
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the order in which tests are executed is changed then test fails.
This commit ensures that all migrations are run before ensuring that
there are no pending migration.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
neerajdotname/make_test_order_independent_by_resetting_timezone
make test order independent by resetting timezone
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | | |
reset default timezone and make test order independent
|
| |/ / / |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
neerajdotname/make_order_independent_association_test
make test not depend on order
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
`NestedThroughAssociationsTest` adds records to `member_details` table.
When test performs `@member_details[0]` then the order of record
is not guaranteed. Hence it is best to start with a clean slate by
deleting unwanted records.
|