Sequel: The Database Toolkit for Ruby | Hacker News Reader

Sequel: The Database Toolkit for Ruby

github.com

63 pointsthunderbong36 comments

To me, the best part about sequel is that it works with jruby. I use it as a secret weapon when I need a db automation that runs practically anywhere thanks to JVM (and thanks to Jeremy).

It's been years since I investigated it but isn't ActiveRecord running in JRuby these days?

Yes, rails targets jruby, so it should be possible to accomplish something similar with activerecord as well. I just like Sequel the way I like Sinatra.

Greetings from another Sinatra lover!

Are you saying it is compitable with JRuby (using a adapter) nowadays or are you saying ActiveRecord runs in a JRuby process when running Rails?

It was a honest question, I was curious if, using JRuby, I could use ActiveRecord as an ORM instead of Sequel. I am not challenging any preference towards Sequel.

Yes you can use either.

I think you might be slightly more limited in your choice of database drivers compared to MRI Ruby but I believe there’s a JDBC driver that should fill the gap.

I wasn't sure about how I should interpret your question or if it was statement, that's why I asked.

Yes, you can use the jdbc adapter made by the JRuby team! https://github.com/jruby/activerecord-jdbc-adapter

Though, in my opinion, the best combo has been Sinatra + Sequel.

> db automation that runs practically anywhere thanks to JVM

Doesn't both JRuby and CRuby require you to download platform specific executable? Or does JRuby offer a portable standalone executable? If that is the case then I might also switch.

You can download the complete JRuby JAR, which will run happily anywhere you have a JVM.

You don't want to distribute JRuby's executable, or your ruby code. To release, what you want to do is to compile your program and all its dependencies (including JRuby's jar file) into a single jar using something like warbler. This also acts as a layer of obfuscation, since JRuby produces code that generates classes dynamically, so it will all look very ugly to the human eye.

Oh I see, thank you!

This is what I reach for whenever I'm not using ActiveRecord in Ruby. Excellent library—difficult to talk about over audio.

> difficult to talk about over audio

:-) Yes, I've had the same problem! They might as well have named the project "The word sequel, as in the next thing, not Ess Cue Ell."

I used this a lot when I wasn't doing any other Ruby at the time, to do some more involved SQL automatization and ETL. I tried to stick with SQL/psql as much as possible, but if that fails or would've lead too much into temporary tables and pl/sql, I went with Sequel. I could fiddle around it in an interactive REPL if I wanted to, and the resulting code wasn't too OO so that the underlying Postgres representation was barely visible.

Some day I might try my hand at a "full Jeremy Evans" stack backend, i.e. both Sequel and his web framework Roda, authentication with Rodauth etc.

I really like Sequel and use it as well in non rails apps. Its powering pg-osc and pg_easy_replicate for me. Thanks for the project!

This is probably my favorite gem of all time. I strongly prefer it to active record. Especially when I have to do any sort of complex query.

Reply on news.ycombinator.com