Cursor rule

1---
2description: Database rules for working with drizzle schemas and creating backend apis
3globs: apps/**/*.ts
4alwaysApply: false
5---
6Leverage strings with drizzle types, instead of enums:
7`status: text("status").$type<pending | cancelled |error >().notNull()`
8 
9Only use varchar for ids, similiar to the users table. Otherwise use text.
10 
11When creating a new table, leverage the id util `packages/id/src/generate.ts`
12<new_table_prefix>
13```ts
14`packages/id/generate.ts`
15 
16const prefixes = {
17  post: "post",
18  property: "prop",
19  // Add new prefixes here
20} as const;
21```
22For generate.ts, all you have to do is add the table name (or varation) as a key to the const. No need to use nanoid or change any other code.
23Also abbreviate longer words, i.e   property: "cust",
24 
25 
26 
27Then inside `packages/db/schema.ts` you can use it like so:
28```ts
29export const properties = pgTable("properties", {
30  id: varchar("id", { length: 255 })
31    .primaryKey()
32    .$defaultFn(() => newId("property"))
33}
34```
35</new_table_prefix>
36 
37Users table doesn't need items like avatar or name, unless specificially required to sync via clerk
38