arproxy

arproxy copied to clipboard

From Rails 6, `ActiveRecord::Base.transaction` does not execute `BEGIN;` and it is executed at the first query of the transaction instead. https://github.com/rails/rails/pull/32647 it seems that this change cause the process order...

shallow1729

Avoid eager loading `ActiveRecord::Base`

1

## Problem When Arproxy is loaded by specifying `Gemfile`, `require "active_record/base"` is called and `ActiveRecord::Base` is loaded. Just when `Rails.application.config.active_record.xxx` are copied to `ActiveRecord::Base.xxx`. So, `config/initializers/new_framework_defaults_x_x.rb` does not work well....

yujideveloper

I followed the [Readonly Access example in the readme](https://github.com/cookpad/arproxy#readonly-access) and found that updates still managed to be written: ``` [9] pry(main)> customer.first_name = "Wheeeee" => "Wheeeee" [10] pry(main)> customer.save From:...

maloneyl

I am encountering an issue with Rails version 7.1.3.2, where certain expected behaviors are not functioning as anticipated. Specifically, the use of ActiveRecord::Base.connection.execute seems to trigger the proxy execution correctly,...

juri-t

Since ActiveRecored 7.1, using `#execute` no longer works as intended. ref https://github.com/rails/rails/commit/63c0d6b31bcd0fc33745ec6fd278b2d1aab9be54#diff-0b861bb8bc857373d0f0280779eb119e2937ee0edd1cc 3497292c7d14e909591 #26 Instead, I have made a change to use `#raw_execute`. Since `#raw_execute` is a private method, I'm...

hirocaster

* Added support for ActiveRecord 7.1. * Redesigned the proxy chain to accommodate internal structure changes in ActiveRecord 7.1. * Introduced integration tests using real databases, allowing for more robust...

mirakui

Developing arproxy v1: integration tests, redesign aiming to fully support for AR7.1+

1

# Background The current latest version of arproxy (v0.2.8) has the following known issues: - Does not work correctly with ActiveRecord 7.0 and later - #26 - CI (unit tests)...

mirakui