| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
`ActiveRecord::ConnectionAdapters::PostgreSQL::SchemaStatements#default_sequence_name`
|
| |
|
|\
| |
| |
| |
| | |
jeremywadsack/use_transactional_fixtures_all_databases
Use notification to ensure that lazy-loaded model classes have transactions
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
loaded model classes have their connections wrapped in transactions.
See #17776
In Rails 4 config.eager_load was changed to false in the test environment. This
means that model classes that connect to alternate databases with
establish_connection are not loaded at start up. If use_transactional_fixtures
is enabled, transactions are wrapped around the connections that have been
established only at the start of the test suite. So model classes loaded later
don't have transactions causing data created in the alternate database not to
be removed.
This change resolves that by creating a new connection.active_record
notification that gets fired whenever a connection is established. I then added
a subscriber after we set up transactions in the test environment to listen for
additional connections and wrap those in transactions as well.
|
|\ \
| | |
| | | |
Add newline between each migration in `structure.sql`
|
| | |
| | |
| | |
| | |
| | |
| | | |
Keeps schema migration inserts as a single commit, so we still get all of the
benefits of https://github.com/rails/rails/commit/42dd2336b31a8d98776d039a2b9fd7f834156a78,
but allows for easier git diff-ing. Fixes #25504.
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| | |
We are setting a limit unconditionally just below,
which overrides any existing one anyway.
|
|/ |
|
|\
| |
| | |
rails -> Rails [ci skip]
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
When `group` is used in combination with any calculation method, the
resulting hash uses the grouping expression as the key. Currently we're
incorrectly always favoring the type reported by the query, instead of
the type known by the class. This causes differing behavior depending on
whether the adaptor actually gives proper types with the query or not.
After this change, the behavior will be the same on all adaptors -- we
see if we know the type from the class, fall back to the type from the
query, and finally fall back to the identity type.
Fixes #25595
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The documentation states that parameter values longer than 20 characters
will be truncated by words, but the example shows that a parameter based
on "David Heinemeier Hansson" (with id: 125) becomes "125-david" when
"David Heinemeier".length == 16 so why so short?
The answer lies in the use of the #truncate option omission: nil which
seems to have been intended to mean "nothing", but which actually causes
the default string "..." to be used. This causes #truncate to cleave
words until the "..." can be added and still remain within the requested
size of 20 characters.
The better option is omission: '' (which is probably what was originally
intended).
Furthermore, since the use of #parameterize will remove non-alphanumeric
characters, we can maximize the useful content of the output by calling
parameterize first and then giving truncate a separator: /-/ rather than
a space.
|
|
|
|
| |
This includes minor grammar fixes throughout the file.
|
|\
| |
| | |
Don't reap connections that have already been reassigned
|
| | |
|
| |
| |
| |
| |
| |
| | |
This way, we aren't racing other threads, so we don't need to re-check
the conditional. And we no longer need to hold the lock while calling
remove (which can choose to make a new connection while we wait).
|
| |
| |
| |
| |
| |
| |
| | |
A concurrent thread may have also detected it to be stale, and already
released (or even reassigned) it by now.
Fixes #25585
|
| |
| |
| |
| |
| | |
A thread can only release a connection if it owns it, or it's owned by a
thread that has died.
|
| | |
|
|\ \
| | |
| | | |
Use `squish` rather than `strip_heredoc`
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
HermanHiddema/fix/unnecessary-nesting-in-handle-dependency
Fixed unnecessary nesting in handle_dependency
|
| |/
| |
| |
| |
| | |
This nested if checked the same value as the containing case statement.
Moved the code in the if/else into when/else in the containing case.
|
|/ |
|
|\
| |
| | |
Improve error message when record touch fails.
|
| |
| |
| |
| |
| |
| | |
The current error message only indicates that a touch can fail because the record is new. In practice, we saw cases where touches were failing because the record had been destroyed. `persisted?` checks `new_record?` *and* `destroyed?`. It was confusing to get a message about a new record when in reality we were destroying records.
I also included a helpful tip for users to consider using `persisted?`, `new_record?`, or `destroyed?` before touching.
|
|/ |
|
|\
| |
| | |
Remove unused `predicate_builder` for `BasicObjectHandler` and `RangeHandler`
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
bquorning/optimize-for-first-result-and-remove-mysql-select_one
Remove #select_one from Mysql2Adapter
|
| | |
| | |
| | |
| | |
| | | |
If you only want the last element of a result set, there's no need to create all
of hash_rows. Also, add a test.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The implementation from abstract/database_statements.rb seems to work just fine.
And with ActiveRecord::Result now implementing an optimized #first method, the
performance concerns previously addressed in
https://github.com/rails/rails/commit/bf79aa4fc14aeb2646331e767038acf0b77e9e7f
should not be an issue.
|
| | |
| | |
| | |
| | |
| | | |
When you only need the first element of a result set, you shouldn't need to
instantiate all of hash_rows.
|
|\ \ \
| | | |
| | | | |
Revert "Rename `active_record_internal_metadatas` to `ar_internal_metadata"
|
| | | |
| | | |
| | | |
| | | | |
This reverts commit 407e0ab5e5cddf6a8b6b278b12f50772d13b4d86.
|
|\ \ \ \
| |_|_|/
|/| | | |
Remove `create_table_info_cache` because it not be reused
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
`create_table_info_cache` is used for sharing `create_table_info` both
`table_options` and `foreign_keys`. But `foreign_keys` no longer uses
`create_table_info_cache` by #25307. No need caching anymore.
|
|\ \ \
| |/ /
|/| | |
Pass `pk: false` to `connection.insert` explicitly if do not have a primary key
|
| | |
| | |
| | |
| | |
| | |
| | | |
Because causing an extra query by `sql_for_insert` for guessing a
primary key.
https://github.com/rails/rails/blob/v5.0.0/activerecord/lib/active_record/connection_adapters/postgresql/database_statements.rb#L121-L125
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
kamipo/extract_foreign_key_action_from_information_schema
Extract foreign key action from `information_schema`
|
| | |
| | |
| | |
| | | |
Fixes #25300.
|
| | | |
|
| | |
| | |
| | |
| | | |
preventing infinite looping in some cases.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Right now with this middleware we are likely always connected, but I'm
hoping to change that soon. This is an easy change to pull out on its
own.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This method appears to have been partially used in connection pool
caching, but it was introduced without much reasoning or any tests. One
edge case test was added later on, but it was focused on implementation
details. This method is no longer used outside of tests, and as such is
removed.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This was added at c7c3f73 but it never raised because MySQL cannot
create text/blob columns with a default value.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As mentioned in 7b86ea6715ee987e61a7f3bd8e72b1bbfcfbbbe7, this is an
internal class.
[ci skip]
r? @sgrif
|