CODEWITHSUNDEEP
node.jstypescriptpostgresqlormprisma
Faig
Faig

Reputation: 43

Why not all of my columns show up in prisma client's types?

I'm using prisma ORM in my node.js project. I code in TypeScript. I have reverse engineered my postgresql database tables into prisma schema. Then I've generated prisma client with npx prisma generate. It has created all of the types that I need to work with the database, but they are not correct. Each table has a pair of types: [tableName]CreateInput and [tableName]uncheckedCreateInput (I don't know what is this one for).

For example my customers table has customersCreateInput and customersUncheckedCreateInput types. The customersCreateInput lacks the id column (this column is the most important one). The customersUncheckedCreateInput has all of the columns including the id, but it is optional there... Why prisma does this, and how can I fix it? I want to make it work correctly every time i run npx prisma generate. Please help me, I have searched google for few days, I've found some corresponding topics (they've discussed different problem but it was about unchecked types in prisma) but didn't understand what they are talking about there.

export type customersCreateInput = {
    customer_email: string
    phone: string
    first_name: string
    middle_name?: string | null
    last_name?: string | null
    password_hash: string
    registered_at: Date | string
    last_login?: Date | string | null
    comments?: string | null
    addresses?: addressesCreateNestedManyWithoutCustomersInput
    carts?: cartsCreateNestedManyWithoutCustomersInput
    order_items?: order_itemsCreateNestedManyWithoutCustomersInput
    orders?: ordersCreateNestedManyWithoutCustomersInput
  }

  export type customersUncheckedCreateInput = {
    id?: number
    customer_email: string
    phone: string
    first_name: string
    middle_name?: string | null
    last_name?: string | null
    password_hash: string
    registered_at: Date | string
    last_login?: Date | string | null
    comments?: string | null
    addresses?: addressesUncheckedCreateNestedManyWithoutCustomersInput
    carts?: cartsUncheckedCreateNestedManyWithoutCustomersInput
    order_items?: order_itemsUncheckedCreateNestedManyWithoutCustomersInput
    orders?: ordersUncheckedCreateNestedManyWithoutCustomersInput
  }

I create that table with this SQL qyery:

CREATE TABLE Customers (
  ID SERIAL PRIMARY KEY NOT NULL,
  Customer_Email varchar(50) UNIQUE DEFAULT null,
  Phone varchar(25) NOT NULL,
  First_Name varchar(40) NOT NULL,
  Middle_Name varchar(40) DEFAULT null,
  Last_Name varchar(40) DEFAULT null,
  Password_Hash varchar(100) NOT NULL,
  Registered_At timestamp NOT NULL,
  Last_Login timestamp DEFAULT null,
  Comments varchar(250) DEFAULT null
);

My generated prisma schema is the one below:

model customers {
  id             Int           @id @default(autoincrement())
  customer_email String        @unique @db.VarChar(50)
  phone          String        @db.VarChar(25)
  first_name     String        @db.VarChar(40)
  middle_name    String?       @db.VarChar(40)
  last_name      String?       @db.VarChar(40)
  password_hash  String        @db.VarChar(100)
  registered_at  DateTime      @db.Timestamp(6)
  last_login     DateTime?     @db.Timestamp(6)
  comments       String?       @db.VarChar(250)
  addresses      addresses[]
  carts          carts[]
  order_items    order_items[]
  orders         orders[]
}

Upvotes: 1

Views: 2707

Answers (1)

Danila
Danila

Reputation: 18526

You have @default(autoincrement()) for id therefore you can let DB do the work and not pass it manually here, it will be controlled automatically on DB level to avoid conflicts and to simplify things for you.

But if you want to pass id you still can do it manually, this is why second type is there, it seems.

prisma generates two different types for some reason, and uses XOR type on them, so you can either use one or another, but not combination of them, like that:

  export type ExampleCreateArgs = {
    /**
     * Select specific fields to fetch from the Example
     * 
    **/
    select?: ExampleSelect | null
    /**
     * The data needed to create a Example.
     * 
    **/
    data: XOR<ExampleCreateInput, ExampleUncheckedCreateInput>
  }

For example, if you want to reuse that data type in your code you can do the following:

// substitute ExampleCreateArgs to correct one from your code
type Data = ExampleCreateArgs["data"]

Upvotes: 2

Related Questions