sequel_pg

Faster SELECTs when using Sequel with pg

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

0Explicit recommenders

270GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Faster SELECTs when using Sequel with pg

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month2 dated mentions

Observed mentions: 2012-06-30 16:38:20 UTC to 2013-03-20 14:38:18 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Jun 2012	2012-06-01 00:00:00 UTC	2012-07-01 00:00:00 UTC	1	1
Jul 2012	2012-07-01 00:00:00 UTC	2012-08-01 00:00:00 UTC	0	0
Aug 2012	2012-08-01 00:00:00 UTC	2012-09-01 00:00:00 UTC	0	0
Sep 2012	2012-09-01 00:00:00 UTC	2012-10-01 00:00:00 UTC	0	0
Oct 2012	2012-10-01 00:00:00 UTC	2012-11-01 00:00:00 UTC	0	0
Nov 2012	2012-11-01 00:00:00 UTC	2012-12-01 00:00:00 UTC	0	0
Dec 2012	2012-12-01 00:00:00 UTC	2013-01-01 00:00:00 UTC	0	0
Jan 2013	2013-01-01 00:00:00 UTC	2013-02-01 00:00:00 UTC	0	0
Feb 2013	2013-02-01 00:00:00 UTC	2013-03-01 00:00:00 UTC	0	0
Mar 2013	2013-03-01 00:00:00 UTC	2013-04-01 00:00:00 UTC	1	1

What Hacker News says

2 sources

robertsosinski·Mar 20, 2013

For quite some time, I have been using Sequel (http://sequel.rubyforge.org) as an ORM with Postgres instead of ActiveRecord, and have never been happier. Overall, Rails has been a great web-framework, but ActiveRecord has been it's sore spot, at least for me. Also, using the sequel_pg (https://github.com/jeremyevans/sequel_pg) on Postgres ensures that even raw SQL queries are type-casted properly, plus it supports streaming and cursors, while also being very very quick. If you want to stick with Ruby/Rails and relational databases, but think ActiveRecord might not be your bag, give Sequel a shot. It also fits nicely into lighter frameworks such as Sinatra.

In Today's Email Incident

chanks·Jun 30, 2012

I love Rails, but I strongly disagree with its philosophy of the DB as being just a dumb data store. Two things I would recommend. One, the book Enterprise Rails. It's a few years old, so all the examples are from Rails 2, but the meat of it is about proper database design, including the stuff that Rails doesn't believe in (composite primary keys, foreign key constraints, check constraints, triggers). Chapter 4, about the importance of data integrity, was probably the single most useful thing I've read about web development in the past few years. Most of it is on Google Books (although sadly, chunks of chapter 4 are missing): http://books.google.com/books?id=thTju-4duY4C&printsec=f... Second, the best thing I did was replace ActiveRecord with Sequel. Sequel has built-in support for all of those things that ActiveRecord doesn't (I couldn't

Read the rest

live without its composite primary key support), and is in general a much more robust library than ActiveRecord. It also supports more exotic SQL features like CTEs and CASE statements without forcing you to drop down to writing raw SQL (though you can certainly do that if you want). It's not a necessary upgrade for everyone. If your app has fairly simple models and relationships, ActiveRecord will probably be just fine for you. But if you want to get better with SQL and get closer to your DB, I think Sequel is a much better choice. More info on Sequel: http://sequel.rubyforge.org/ It also integrates very well with Postgres - there's a C extension for the Sequel postgres adapter (https://github.com/jeremyevans/sequel_pg) and support for adding common triggers in migrations, counter columns and whatnot (https://github.com/jeremyevans/sequel_postgresql_triggers). It also supports the more exotic datatypes - hstore, arrays, even the json and range types that are coming in PG 9.2.

In Ask HN: How can I learn "advanced" data modelling for Rails?