sequel-activerecord_connection

Allows Sequel to reuse Active Record's database connection (by janko)

Sequel-activerecord_connection Alternatives

Similar projects and alternatives to sequel-activerecord_connection

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better sequel-activerecord_connection alternative or higher similarity.

sequel-activerecord_connection reviews and mentions

Posts with mentions or reviews of sequel-activerecord_connection. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-12.
  • What It Took to Build a Rails Integration for Rodauth
    11 projects | dev.to | 12 Oct 2022
    For the integration to work, I would need to make Sequel reuse Active Record's database connection. I discussed this idea with Jeremy Evans (the lead Sequel maintainer), and he provided me with some guidance, thanks to which I was able to come up a solution. It was a Sequel extension that retrieved Active Record connections, kept transaction state and callbacks synchronized between Sequel and Active Record, integrated SQL instrumentation, and reconciliated adapter differences (see my previous article for more details).
  • Why Sequel ORM faster than ActiveRecord
    2 projects | /r/ruby | 20 Feb 2022
    Our Rails app at work is using Active Record, but I started non-apologetically using Sequel for any features I'm missing from Active Record, because I don't have the patience for Active Record to catch up. For our analytics database we're using only Sequel, because AR was missing too many features (see my article), while for our main database we're using it in tandem with Active Record, reusing Active Record's database connection. I'm pretty happy that the latter is now possible, as it gives people the opportunity to try out Sequel without any overhead.
  • Ruby gem for authentication : rodauth
    2 projects | /r/ruby | 11 Jan 2022
    The way I look at it, a pure Active Record implementation could never be fully complete. That's why I instead chose the path of making Sequel integrate seamlessly with Active Record, by sharing a database connection as /u/honeyryderchuck said, hooking into Active Record's query instrumentation, and also by making Sequel transactions interoperable with Active Record's. It's also worth noting that core Sequel is significantly lighter than Active Record.
  • How does Ruby's OOP translate to Rails?
    2 projects | /r/ruby | 4 Sep 2021
    the main impediments to my using sequel in Rails are: authentication - which has largely been solved. Janko has written a gem allowing for rod auth to be used with rails, easily. https://github.com/janko/rodauth-rails - i believe he has also written another gem to make it easy to use sequel in a rails app https://github.com/janko/sequel-activerecord_connection
  • Sqlcomposer Early Preview Answering Questions
    1 project | /r/ruby | 2 Jan 2021
    From a user's perspective, I've always found the fact that rom-sql uses Sequel under-the-hood as a big advantage. For someone who is familiar with Sequel it lowers the barrier of understanding how rom-sql works. And it's possible to leverage many of Sequel's useful features that rom-sql might not support OOTB (including performance optimizations such as sequel_pg), even if that requires dropping to the Sequel database level. When I announced sequel-activerecord_connection, one of the questions I received was whether that will work with rom-sql too (and it does).
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 26 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic sequel-activerecord_connection repo stats
5
125
6.1
17 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com