Incorrect casing for “ID”

All implicit generated IDs such as the ID for Foo is generated as FooId. While much of the documentation uses “ID”, the code representation is incorrect casing where “ID” is the standard abbreviation form for identifiers (IDs), not “Id”. Changing this would align other correctly-cased variables in the project like DB (along with uses of IO, UUID, & FromJSON from other libs), but still leaves incorrect cases like Sql instead of SQL for the initialism ‘structured query language’ (where documentation is largely using “SQL”).

What I would expect is the implicit ID for Foo becomes FooID… all fooId columns become fooID.

Moving from ‘ID’ to ‘Id’ is losing valuable casing information & if it weren’t important, we wouldn’t be bothering with upper case letters at all in English (& other languages with bicameral scripts). …It is also a bit Freudian to use “Id”.

The issue does not name files or tests, so first locate the entry points for implicit ID generation and generated column naming. Assess the impact across the persistence interface and its storage methods, including compatibility with existing FooId and fooId names; done means the agreed ID casing is generated consistently without unaddressed cases.