Tedious best practices?

[tyleralbee]

I'm hoping to stimulate some discussion on best practices for tedious, and more generally, database services as a whole.

• How are you structuring your projects?
• What does a typical service look like in your server?
• Have you experienced any difficulty around ESM when using tedious or a derivative? How are you bundling your project, if at all?

I'll share some stuff I've made in my own projects to get the conversation going.

I'm a big fan of Zod and I wrote up some schema that define the translation between SQL Server data types and the ones that tedious converts to in JavaScript.

Here's the one for tinyint:

/**
 * T-SQL `tinyint` datatype
 *
 * @remarks
 * 0 to 255
 * @remarks
 * JS type coercion by `tedious` - `Number`
 * @see {@link https://learn.microsoft.com/en-us/sql/t-sql/data-types/int-bigint-smallint-and-tinyint-transact-sql?view=sql-server-ver16}
 */
const tinyint = z.number().int().min(0).max(255);

Since I've got all of the SQL Server data types defined like this, I can model my database tables as Zod schema like this:

const SomeTablePrimaryKey = Symbol("PK_SomeTable");

export const SomeTable = z.object({
    Id: tsql.smallint.brand(SomeTablePrimaryKey),
})

What are you building lately?