4 ms·
Sequel: The Database Toolkit for Ruby
- Alifatisk 2y ago[flagged]
- thunderbong 2y agoSequel 5.84.0 Changelog https://github.com/jeremyevans/sequel/discussions/2212 https://github.com/jeremyevans/sequel/discussions/2212
- ejflick 2y agoSequel 5.83.0 Changelog https://github.com/jeremyevans/sequel/discussions/2198 https://github.com/jeremyevans/sequel/discussions/2198
- thibaut_barrere 2y agoNot the OP, but the number of people actually knowing about it and/or using it is quite low, and I feel it is one of the most underrated & powerful libraries in the Ruby world!
- Alifatisk 2y agoReally? That totally changes my assumption. I thought it was a well known gem. I reach out to when whenever I want to automate some database related tasks OR when I want to know if there is a better way to write a sql query.
- thibaut_barrere 2y agoMost Rubyists I know barely know it (well they have "heard" of it, but not actually used it)!
- Alifatisk 2y agoThey are missing out!
- thibaut_barrere 2y agoHell yes :-) For the record, I am a deep Sequel fan, and wrote ETL connectors that use it: https://www.kiba-etl.org/kiba-pro https://www.kiba-etl.org/kiba-pro https://github.com/thbar/kiba/wiki#kiba-pro https://github.com/thbar/kiba/wiki#kiba-pro (full doc with snippets) It is one of the most underrated gems of the Ruby universe IMO!
- Lanfgh 2y ago[flagged]
- yreg 2y ago[flagged]
- 0xEF 2y agoNot everyone pronounces SQL as 'sequel,' since it is a known acronym, so don't go thinking that's widely accepted because a vocal bunch on YouTube says 'sequel.' Still, it was dumb to name another project that.
- ssss11 2y agoAs another data point - I’ve never looked at YouTube for database content, but every single DBA I’ve encountered in the corporate world pronounces SQL as ‘sequel’.
- 0xEF 2y agoAnecdotal, but fair, since I can say the opposite. I've largely heard it said as S Q L, ro the point when someone verbally calls it "sequel" it takes me an extra moment to remember what they are referring to. I rationalize it thus; we don't make words from our other acronyms that aren't already pronouncable words to some degree. Exploring that, we don't say "fibby" when we mean FBI or "see ya" when we mean CIA (maybe we should, though?). DARPA, on the other hand, is pronouncable on its own, so we'll say the word instead of D A R P A. Another one is HIPAA, which is interesting, since its pronouncable, but people often get the acronym wrong as HIPPA when writing/typing it (FAFSA being another good example) although that is more US-centric. Anyway, our treatment of saying the word instead of saying the letters of the acronym is interesting to think about, I guess. I reckon there's a lot of cultural and linguistic influence there. Perhaps someone smarter than me can unpack it.
- ssss11 2y agoIt is interesting. I always thought it began as ’sequel’ and was then abbreviated, but I wasn’t around when it started back in the 1960’s or whenever that was… might go google it haha
- nurettin 2y agoTo 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).
- pantulis 2y agoIt's been years since I investigated it but isn't ActiveRecord running in JRuby these days?
- nurettin 2y agoYes, 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.
- pantulis 2y agoGreetings from another Sinatra lover!
- Alifatisk 2y agoAre you saying it is compitable with JRuby (using a adapter) nowadays or are you saying ActiveRecord runs in a JRuby process when running Rails?
- pantulis 2y agoIt 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.
- Lio 2y agoYes 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.
- neallindsay 2y agoThis is what I reach for whenever I'm not using ActiveRecord in Ruby. Excellent library—difficult to talk about over audio.
- knodi123 2y ago> 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."
- shayonj 2y agoI 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!
- deleted 2y ago[deleted]
- cooljacob204 2y agoThis 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.
- mhd 2y agoI 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.