sivers

store

Ruby2019–2025

sivers / store

store

PostgreSQL shopping cart

Data & Databases

Explore on GitHub Read Hacker News discussions

5Distinct people

7Mentions

1Explicit recommenders

275GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

PostgreSQL shopping cart

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

> How? Stored procedures? Not neccesarily. jOOQ[1] and sqlc[2] are great options if you don't like stored procedures, but for a small app or a prototype, just having plain SQL…

taffer used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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:03:16 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 year7 dated mentions

Observed mentions: 2019-10-27 15:48:10 UTC to 2025-10-13 09:44:55 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	Submissions	Comments
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	0	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	2	0	2
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	0	1
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	1	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	2	0	2

What Hacker News says

7 sources

taffer·Oct 13, 2025Recommendation phrase

> How? Stored procedures? Not neccesarily. jOOQ[1] and sqlc[2] are great options if you don't like stored procedures, but for a small app or a prototype, just having plain SQL strings in your app is fine. My point isn't that the code has to be stored in the database, but rather that the processing happens in one place where your data is stored and your middle tier just gets the results. Pure, stateless data. This means you don't have to synchronise shared mutable state between your app and your DB server, cutting out all the headaches of ORMs, such as having to specify your data model in two separate places, n+1 queries, locking, lifecycle management, dirty tracking, eager loading, caching, and optimistic concurrency control. All of this adds to complexity and congnitive load. SQL also provides a declarative approach to defining your busi

Read the rest

ness logic. You define the what, not the how. In addition to greater productivity, the programming model is much simpler because you aren't complecting control flow with data flow. With JSON support in Postgres, your query results don't have to be flat tables either. You can get your data in the exact shape you need. > How do you version that code You put it into your VCS. SQL is part of your code base, you can and should version control it just like any Python, Ruby or Java code. When using stored procedures, I recommend putting them in a separate schema, so that the schema can be dropped and recreated in a single transaction during deployment. See [3] for an example of stored procedures under version control. > how do you reason with the business logic split all over the DB and code You separate your concerns instead of mixing them. The core business logic is in SQL, with your middle tier doing the plumbing, orchestration of external services and presentation. [1] https://www.jooq.org/ [2] https://sqlc.dev/ [3] https://github.com/sivers/store

In Django: One ORM to rule all databases

taffer·Sep 5, 2025

Putting business logic in the database: https://sive.rs/pg Example code: https://github.com/sivers/store This talk is more Oracle specific but with some minor changes you can apply the same ideas to postgres: https://www.youtube.com/watch?v=GZUgey3hwyI Personally I am using an architecture similar to https://sive.rs/pg in my personal projects and I am very happy with it. It is important that you put data and procedures/views in different schemas so that you can use migrations for your data but automatically delete and recreate the procedures/views during deployment. Also use pgtap or something similar for testing.

In SQL needed structure

tosh·Sep 22, 2024Submission

PostgreSQL Shopping Cart

2 points · Open discussion

0xCMP·Apr 21, 2023

I would agree, but I think it's worth checking out one of Siver's postgres repos where I thought he tested things pretty well[0]. Also things like Postgres are often run as a "server" on local dev or CI but could easily be run more ephemerally[1]. That should help with testing various states and behavior of the database. I still would actually follow what you said thought because often times places which rely on stored procedures are, as you say, ruled by developers with the database access to manage those procedures and from what I've seen often do not have anything close to a reproducible setup. Besides the fact that often it's some proprietary database which is much more difficult to run locally than sqlite3 or PostgreSQL. Still I keep that separate from considering if views/stored procedures are actually a good solution. I think somet

Read the rest

imes it really is. Honestly Sivers' experiments really convinced me of that. [0]: https://github.com/sivers/store [1]: https://jamey.thesharps.us/2019/05/29/per-project-postgres/

In Use databases without putting domain logic in them

sivers·Aug 24, 2022

Cool! I do this, but I haven't seen anyone else do it. Is any of your code public? I wrote about it at https://sive.rs/pg and posted my SQL shopping cart at https://github.com/sivers/store Please contact me if you'd like to share tips: https://sive.rs/contact

In A Critique of SQL, 40 Years Later

chubot·Feb 9, 2022

Also: https://sive.rs/pg2 - Simplify: move code into database functions https://sive.rs/pg - PostgreSQL example of self-contained stored procedures some linked examples: https://github.com/sivers/store/tree/master/store/functions I like this idea in theory ... although it would cause me to need to know a lot more SQL, which is a powerful but hostile language :-/ I care about factoring stuff out into expressions / functions and SQL fails in that regard ... https://www.scattered-thoughts.net/writing/against-sql/ It's hard to imagine doing this with a ton of duplication. I have written SQL by hand and there are probably more confusing corners than in shell, which is saying a lot!

In Single dependency stacks

sivers·Oct 27, 2019

I'm the author. Thanks to Ludwig for posting this here. I've been doing all of my database work like this for 5+ years now, and love it. Many more examples here: https://code.sivers.org/db-api/ It works great when you want to write simple shell scripts, too. They look as simple as this: https://github.com/sivers/store/blob/master/getdb-example.rb... People have been asking how I do unit testing. The main thing is to have a fixtures.sql file, which is a dump of data to test against: https://github.com/sivers/store/blob/master/store/fixtures.s... Then in the setup before each unit test, just drop the database schema, and reload it: https://github.com/sivers/store/blob/master/test_tools.rb?ts... Examples of my API unit tests here: https://github.com/sivers/store/blob/master/store/test-api.r... And also testing things like database trigger

Read the rest

s, and private functions: https://github.com/sivers/store/blob/master/store/test-db.rb... Feel free to ask me anything here, or email me: https://sivers.org/contact — Derek

In PostgreSQL example of self-contained stored procedures