PostgreSQL Development Standards FAQs

Question 1

Does this skill work with specific ORMs?

Accepted Answer

While the principles apply to any PostgreSQL development, it includes specific concrete patterns and guidance for TypeScript and the Drizzle ORM.

Question 2

What is the TX_ prefix rule in this skill?

Accepted Answer

It is a naming convention where any method that explicitly starts a new database transaction must be prefixed with 'TX_'. This prevents nested transaction errors and makes transaction boundaries visible in the code.

Question 3

Why does this skill recommend ULIDs over standard UUIDs?

Accepted Answer

ULIDs are recommended because they are time-sortable, which improves indexing efficiency in PostgreSQL while still providing the security benefits of being non-enumerable like a UUID.

Question 4

How does this skill handle financial data?

Accepted Answer

It strictly forbids the use of float or double types for money. Instead, it enforces the use of exact numeric/decimal types to ensure precision and prevent accumulated rounding errors.

Question 5

What is the benefit of read-write separation at the type level?

Accepted Answer

By maintaining separate client types, the skill prevents accidental mutations on read-only replicas and forces developers to be deliberate when performing write operations.

PostgreSQL Development Standards

主要功能

使用场景

PostgreSQL Development Standards

主要功能

使用场景