jeremyevans/sequel

Sequel: The Database Toolkit for Ruby

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 12 minutes ago
Added to GitGenius on September 13th, 2026
Created on March 31st, 2008
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 1,073
Total Stargazers: 5,094 (+0)
Total Subscribers: 107 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Sequel is a database toolkit for Ruby that provides a DSL for constructing SQL queries, an ORM layer for mapping records to objects, and connection pooling with thread safety.

Sequel solves the problem of verbose and error-prone database access in Ruby by abstracting SQL construction and record management into a chainable, composable API. The toolkit uses datasets as its core abstraction—objects that encapsulate SQL queries and support method chaining to build complex queries incrementally. Rather than writing raw SQL strings, developers construct queries using Ruby methods like where, select, and join, which are translated to SQL only when executed. Records are fetched as hashes and accessed through an Enumerable interface, allowing lazy evaluation and reuse of query objects.

Sequel suits projects that need flexible database access without the overhead of heavier ORMs. It works well for applications requiring advanced database features such as prepared statements, savepoints, two-phase commit, transaction isolation, and primary/replica configurations. The toolkit supports a wide range of databases through dedicated adapters for MySQL, PostgreSQL, SQLite, Oracle, and others. Developers choosing Sequel should expect a lower-level, more explicit approach to database interaction compared to frameworks that hide SQL entirely, but gain fine-grained control and the ability to leverage database-specific capabilities when needed.

The project maintains a stable, long-running codebase with consistent engagement on GitHub Discussions for user questions and GitHub Issues for bug reports. Development activity shows regular maintenance and incremental improvements rather than rapid feature churn, reflecting a mature toolkit focused on reliability and compatibility across its supported database adapters.