Records: SQL for Humans
Records is a simple library for making raw SQL queries to most relational databases. It's powered by SQLAlchemy, but you'd never know it. No ORM. No models. Just SQL in, results out.
$ uv add records
What It Looks Like
import records
db = records.Database("postgres://user:pass@localhost/mydb")
# Run a query.
rows = db.query("SELECT * FROM users WHERE active = true")
# Iterate over results.
for row in rows:
print(row.name, row.email)
# Access columns by name or index.
first = rows[0]
print(first.name)
print(first["email"])
# Parameterized queries. Always use these.
rows = db.query(
"SELECT * FROM users WHERE city = :city AND age > :age",
city="Portland",
age=25,
)
# Export to CSV.
print(rows.export("csv"))
# Export to JSON.
print(rows.export("json"))
# Export to Excel.
with open("report.xlsx", "wb") as f:
f.write(rows.export("xlsx"))
# Export to a pandas DataFrame.
df = rows.export("df")
Connect, query, export. The full Tablib integration means your query results can become CSV, JSON, Excel, YAML, or a DataFrame with a single method call.
The Philosophy
Sometimes you don't need an ORM. You know SQL. Your database knows SQL. The only thing standing between you and your data is boilerplate. Records removes the boilerplate.
It supports PostgreSQL, MySQL, SQLite, Oracle, MS-SQL, and Redshift. You bring the driver, Records brings the interface. Database URLs work the same way they do in dj-database-url and every twelve-factor app you've ever deployed.
The Story
Records came from my time at Heroku, where talking to databases was something every application did and every developer did slightly differently. I wanted a library where the code looked like what you were doing: connect to a database, run a query, get the results. Three lines for three actions.
The export integration with Tablib was the part that surprised me. Once your query results can become any tabular format with a single method call, a lot of "reporting" and "data pipeline" tasks collapse into a few lines of Python. That accidental synergy between two libraries I'd written years apart taught me something about how good abstractions compose.
Records is proof that not everything needs to be an ORM. Sometimes the most powerful interface is the one that gets out of the way and lets you write the SQL you were going to write anyway.
Install
$ uv add records
Database drivers are not included. Install the one you need:
$ uv add psycopg2 # PostgreSQL
$ uv add pymysql # MySQL
Resources
Related
- Tablib — The dataset library that powers Records' export functionality.
- dj-database-url — Database URLs for Django, born from the same Heroku-era thinking.
- From HTTP to Consciousness — The "for humans" philosophy applied everywhere.
- The Lego Bricks Era — The golden era that produced these libraries.