The StripeCustomer table has the same issue. There's both an `id` column and a unique `customerId` column. Presumably the `id` column is useless and could be removed.
Also, is there a way to set up foreign key constraints on `userId` with this ORM? That seems like another oversight.
Also, is there a way to set up foreign key constraints on `userId` with this ORM? That seems like another oversight.