pluralize VS madatdata

> The primary key column is named id or thing_id or thingId, where thing is the singular form of the table name.

Is it naming relations in plural a common thing in practice?

I thought best-practice was to name relations either singular (as each tuple represents one entry) or uninflected (still singular for most words), specially when you're not a fluent speaker of the language being used to name the relations of the database.

Plurals are often irregular for commonly used words, and the fact that this requires a external dependency ( https://github.com/plurals/pluralize ) to cover for some "common plurals" is telling that supporting this feature is a complex thing indeed - that would not be required in the first place with singular everywhere.

You might like what we're building with Seafowl [0], which is an open-source, single binary database you can deploy to the edge for executing cache-friendly queries (so e.g. you can deploy to fly.io free tier, load your data into it, and put Cloudflare in front of it to cache query results like any other HTTP response).

Here's an example [1] multi-page site with Next.js and Seafowl.

[0] https://seafowl.io/docs/getting-started/introduction

[1] https://github.com/splitgraph/madatdata/tree/main/examples/r...

If you're interested, this is the "absolute minimum" React project I was able to create, using `esbuild` (see `dev.mjs`) and some .html files. [0] It's a sub-package in a larger workspace, so there is some complexity inherited from the monorepo in terms of tsconfig.json and dependency management, but you can ignore that; the esbuild part was pleasantly simple to implement, and it pretty much "just works," such that each file in `www` is an entrypoint with one corresponding script from `pages/` that calls `createRoot(container).render()`.

[0] https://github.com/splitgraph/madatdata/tree/main/packages/t...