-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql_mode
specification is not applied in ActiveRecord v7.0.6
#54
Comments
lorint
added a commit
to lorint/activerecord-trilogy-adapter
that referenced
this issue
Jul 19, 2023
lorint
added a commit
to lorint/activerecord-trilogy-adapter
that referenced
this issue
Jul 19, 2023
lorint
added a commit
to lorint/activerecord-trilogy-adapter
that referenced
this issue
Jul 19, 2023
lorint
added a commit
to lorint/activerecord-trilogy-adapter
that referenced
this issue
Jul 19, 2023
Hi, Tomohiko Mimura! Thank you for your research with this issue. Have put together PR #56 with hopes it might offer a comprehensive fix. Many thanks for your contributions to ActiveRecord Trilogy Adapter! |
lorint
added a commit
to lorint/activerecord-trilogy-adapter
that referenced
this issue
Jul 19, 2023
bensheldon
added a commit
that referenced
this issue
Aug 12, 2023
Fixes #54 - Apply connection configuration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
It seems that various settings including
sql_mode
are not applied correctly because configure_connection is not executed.Expected behavior
Both
mysql2
andtorilogy
,sql_mode
is correctly applied as specified in the DB connection settings variables.Actual behavior
mysql2
correctly applies sql_mode.However,
trilogy
applies the default sql_mode.It seems to be due to the fact that the Trilogy Adapter assumes rails/rails#44591.
Current release versions, including Rails v7.0.6, do not include this fix and will not work properly.
System configuration
Rails version: v7.0.6
Ruby version: v3.2.2
trilogy version: v2.4.1
activerecord-trilogy-adapter: v3.1.0
The text was updated successfully, but these errors were encountered: