| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a bug when merging relations of different classes.
```
Given:
Post.joins(:author).merge(Author.order(name: :desc)).to_sql
Before:
SELECT "posts".* FROM "posts"
INNER JOIN "authors" ON "authors"."id" = "posts"."author_id"
ORDER BY "posts"."name" DESC
After:
SELECT "posts".* FROM "posts"
INNER JOIN "authors" ON "authors"."id" = "posts"."author_id"
ORDER BY "authors"."name" DESC
```
|
|
|
|
|
|
|
|
| |
constant"
This reverts commit fbcd46b1a0d255a34d29caa77bbd31c287446333.
This is not needed anymore. See 7280965
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 22f80ae57b26907f662b7fd50a7270a6381e527e.
See
https://github.com/rails/rails/commit/22f80ae57b26907f662b7fd50a7270a6381e527e#commitcomment-4640676
Conflicts:
activerecord/CHANGELOG.md
|
|
|
|
|
|
| |
This is a follow-up to 3053fee954c1e28b23f7e00921d7b9b3b3867fa5.
> The `master` branch should use the `master` branch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this resolves the following error when running `bundle install`
```
ArgumentError: wrong number of arguments (2 for 1)
/Users/senny/Projects/rails/.bundle/bundler/gems/arel-454a25f18c95/lib/arel/crud.rb:5:in `compile_update'
```
The build is still broken with lots of:
```
ArgumentError: wrong number of arguments (2 for 1)
/Users/senny/Projects/rails/.bundle/bundler/gems/arel-454a25f18c95/lib/arel/crud.rb:5:in `compile_update'
```
|
|\
| |
| | |
[ci skip] `apropriate` => `appropriate`, spaces added
|
|/ |
|
|\
| |
| | |
Fixed typos in "shallow routes" and "routing concerns" in routing.md [ci skip]
|
| |
| |
| |
| | |
Grammatical tense correction: "There exists two" => "There exist two".
Plurality correction: "can be reused inside others resources" => "can be reused inside other resources".
|
|\ \
| |/
|/| |
`skiping` => `skipping` [ci skip]
|
|/ |
|
|\
| |
| | |
added test cases to find notes in a file with .builder extension
|
| | |
|
|\ \
| | |
| | | |
Do not count query for all_constraints and all_tab_cols tested with Oracle
|
|/ / |
|
|\ \
| | |
| | | |
Address test_merging_where_relations failure by adding order
|
|/ / |
|
| |
| |
| |
| |
| | |
This will help identify these tasks exists, since they are easier to
setup things for running all AR tests.
|
| |
| |
| |
| | |
Fix travis failures.
|
|\ \
| | |
| | | |
Drop unused param `should_be_quoted` to `PostgreSQLColumn#array_to_string`
|
| |/ |
|
|\ \
| |/
|/| |
[ci skip]updated documentation: added sass and less extensions
|
|/ |
|
| |
|
|\
| |
| | |
Build fix for ruby 1.9.3 syntax
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Checks to see if the record contains the foreign_key to set the inverse automatically
Conflicts:
activerecord/CHANGELOG.md
|
| |
| |
| |
| | |
automatically
|
|\ \
| | |
| | | |
Track initializer's loaded event per file
|
|/ /
| |
| |
| |
| |
| | |
In order to simplify profiling loading of initializers,
added instument for tracking load config initializer event from
`config/initializers`
|
|\ \
| | |
| | | |
avoiding iterations and calling of underscore on all elements of array
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Test order dependency fixes
|
| | |
| | |
| | |
| | | |
FoxyFixturesTest#test_ignores_belongs_to_symbols_if_association_and_foreign_key_are_named_the_same
|
| | |
| | |
| | |
| | | |
test/cases/validations/i18n_generate_message_validation_test.rb and test/cases/validations/uniqueness_validation_test.rb
|
|\ \ \
| | | |
| | | | |
[ci skip] typo in ArgumentError in 4_0_release_notes.md
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
[ci skip] Update gem versions for 3.2 and 3.1. Also change some words.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Use set_backtrace instead of @backtrace in ActionView error
|
| | | | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Change Relation#all to Relation#load [ci skip]
|
| |/ / / |
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
dougbarth/dont_swallow_exceptions_during_transactional_statements_in_mysql
Don't swallow exceptions in transctional statements
|
| | | |
| | | |
| | | |
| | | | |
From PR, @tenderlove would prefer to not maintain these tests.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The MySQL connection adapater swallows all StandardError exceptions,
which includes Mysql::Error and Mysql2::Error. The comment in the
exception clause claims errors thrown here indicate that transactions
aren't supported by the server but that isn't necessarily true. It's
possible the MySQL server has gone away and swallowing a failed commit
may let the application return a successful response when the data has
not been saved. Also, replication libraries like Galera require that the
application handle exceptions thrown at BEGIN/COMMIT.
I'm unable to determine what version of MySQL threw an exception for
transactional statements. I tried as far back as 3.23.49 with InnoDB
disabled but BEGIN & COMMIT statements do not throw an error. If there's
a real case for this logic to continue, we could instead push this
behavior into a configuration setting.
The exception swallowing has been there since the beginning:
db045dbbf60b53dbe013ef25554fd013baf88134
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Explicitly exit with status "1" for create and drop task failures
Conflicts:
activerecord/CHANGELOG.md
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* A non-zero exit status allows subsequent shell commands to be chained
together such as: `rake db:reset test:prepare && rspec && cap deploy`
(if you're feeling brave :)
* Any exceptions raised during the `create` and `drop` tasks are caught
in order to print a "pretty" message to the user. Unfortunately doing
so prevents rake from aborting with a non-zero exit status to the shell.
* Therefore we re-raise the exceptions after the "pretty" message and
re-catch them in the task.
* From the task we explicitly exit with a non-zero status. This method
was chosen (rather than just letting rake fail from the exception) so
that the backtrace is suppressed and the output to stderr is
unchanged.
* Update activerecord CHANGELOG
|