profane-words VS pluralize

the list is too large for it to sensibly fit in primary memory (CPU cache -- not RAM) you can design you data structure to help the CPU/computer prefetch or at least build your list more sensibly. Consider a radix tree if you need higher performance but if you are running single-threaded, you should ignore the locks and just go wild! here is a list of profanities: zacanger/profane-words

> 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.