pudo/dataset

Easy-to-use data handling for SQL data stores with support for implicit table creation, bulk loading, and transactions.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 14th, 2026
Created on April 1st, 2013
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 297
Total Stargazers: 4,870 (+0)
Total Subscribers: 101 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 34.4 days
Mean response time: 319.0 days
90th percentile: 1229.7 days
Tracked items: 18

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,298 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

dataset is a Python library that simplifies reading and writing data in SQL databases by treating them like JSON files.

The library solves the friction of working with relational databases by eliminating boilerplate code. Instead of writing SQL queries and managing schema definitions upfront, dataset allows developers to insert data into tables that are created implicitly on first use. It handles the mapping between Python objects and database rows transparently, supporting bulk loading operations and transactions. This approach lets developers focus on data manipulation rather than database administration.

dataset suits projects where rapid prototyping or exploratory data work takes priority over strict schema enforcement. It works well for scripts, data pipelines, and applications where the database serves as a simple persistence layer rather than a complex relational system. The tool is particularly valuable when you want to avoid the setup overhead of traditional ORMs or raw SQL while still using a proper database backend instead of flat files.

The project maintains a stable, focused scope. Development activity shows consistent attention to the codebase with regular updates addressing issues and maintaining compatibility. The tool has undergone a deliberate architectural change, with data export functionality extracted into a separate package to keep the core library lean and single-purpose.