Created by: dependabot-preview[bot]
Bumps activerecord from 6.1.2.1 to 6.1.3.
Release notes
Sourced from activerecord's releases.
6.1.3
Active Support
- No changes.
Active Model
- No changes.
Active Record
Fix the MySQL adapter to always set the right collation and charset to the connection session.
Rafael Mendonça França
Fix MySQL adapter handling of time objects when prepared statements are enabled.
Rafael Mendonça França
Fix scoping in enum fields using conditions that would generate an
IN
clause.Ryuta Kamizono
Skip optimised #exist? query when #include? is called on a relation with a having clause
Relations that have aliased select values AND a having clause that references an aliased select value would generate an error when #include? was called, due to an optimisation that would generate call #exists? on the relation instead, which effectively alters the select values of the query (and thus removes the aliased select values), but leaves the having clause intact. Because the having clause is then referencing an aliased column that is no longer present in the simplified query, an ActiveRecord::InvalidStatement error was raised.
An sample query affected by this problem:
Author.select('COUNT(*) as total_posts', 'authors.*') .joins(:posts) .group(:id)
... (truncated)
Changelog
Sourced from activerecord's changelog.
Rails 6.1.3 (February 17, 2021)
Fix the MySQL adapter to always set the right collation and charset to the connection session.
Rafael Mendonça França
Fix MySQL adapter handling of time objects when prepared statements are enabled.
Rafael Mendonça França
Fix scoping in enum fields using conditions that would generate an
IN
clause.Ryuta Kamizono
Skip optimised #exist? query when #include? is called on a relation with a having clause
Relations that have aliased select values AND a having clause that references an aliased select value would generate an error when #include? was called, due to an optimisation that would generate call #exists? on the relation instead, which effectively alters the select values of the query (and thus removes the aliased select values), but leaves the having clause intact. Because the having clause is then referencing an aliased column that is no longer present in the simplified query, an ActiveRecord::InvalidStatement error was raised.
An sample query affected by this problem:
Author.select('COUNT(*) as total_posts', 'authors.*') .joins(:posts) .group(:id) .having('total_posts > 2') .include?(Author.first)
This change adds an addition check to the condition that skips the simplified #exists? query, which simply checks for the presence of a having clause.
Fixes #41417
Michael Smart
Increment postgres prepared statement counter before making a prepared statement, so if the statement is aborted without Rails knowledge (e.g., if app gets kill -9d during long-running query or due to Rack::Timeout), app won't end
... (truncated)
Commits
-
5aaaa16
Preparing for 6.1.3 release -
4f5e6b5
Revert "Merge pull request #41232 from code4me/fix-malformed-packet-master" -
eddb809
Merge pull request #41441 from jonathanhefner/apidocs-inline-code-markup -
2a7ff0a
Merge pull request #41419 from smartygus/activerecord-findermethod-include-wi... -
442c6f1
Merge PR #41356 -
48af94b
Merge pull request #41394 from afrase/recursive-association-fix -
2ca0d66
Fix string quotes -
8d825b5
Make we always type cast TimeWithZone objects before passing to mysql2 -
d0f5164
Merge branch '6-1-sec' into 6-1-stable -
fedd535
Merge pull request #41319 from kamipo/fix_scoping_to_take_only_equality - See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language -
@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)