makara
makara copied to clipboard
instacart
A Read-Write Proxy for Connections; Also provides an ActiveRecord adapter.
Hey guys thanks for all the hard work, I'm wanting to upgrade a rails app to ruby 3 but am failing on makara: ```bash /usr/local/dev//rails/vendor/bundle/ruby/3.0.0/gems/activerecord-6.0.4.7/lib/active_record/connection_adapters/mysql/database_statements.rb:19:in `query' /usr/local/dev//rails/vendor/bundle/ruby/3.0.0/gems/activerecord-6.0.4.7/lib/active_record/connection_adapters/abstract/database_statements.rb:102:in `query_values' /usr/local/dev//rails/vendor/bundle/ruby/3.0.0/gems/activerecord-6.0.4.7/lib/active_record/connection_adapters/abstract/schema_statements.rb:62:in `table_exists?'...
We've just rolled out Makara on Rails 7.1, unfortunately it appears broken with all requests going to the primary server. Raising in case any one else plans on rolling out....
Rails 7.1 warns that `ActiveRecord::ConnectionAdapters::SchemaCache` will be removed in Rails 7.2. I tried to look around at what was being returned by `ActiveRecord::ConnectionAdapters::SchemaCache` and try to rebuild the exact same...
Hey, this should fix kind of an obscure error coming from the connection wrapper when an error condition is met. For example, in my case, this error is thrown when...
Why does Makara harshly handle a validation error. A connection should not be blacklisting based on validation.   
I have a Redmine cluster with one master and two slaves running Postgres 9.5 on FreeBSD servers, and everything works as expected when everything is up. (Updates go to the...
Morning! Very quick question/issue here. I've tried switching from mysql to makara adapter in `database.yml` and all seemed to work fine at first. ``` production: database: ***** pool: ** username:...
I couldn't find anything in the documentation or code so my apologies if I've overlooked something, but is there a way to determine programmatically what specific database connection is used...
Hi, We are currently using Makara v0.5.1 which was supposed to fix all warnings to update to Ruby 3. When analyzing the warnings in our codebase I've noticed this ```...
This is just a concept, but i think an important one to have...
