Error validating: You defined the enum `UserRole`. But the current connector does not support enums.

A

Amit•8/8/23, 12:54 AM

is it using sqlite connector ? as the error says, all connectors donot support enum. sqlite doesn't afaik

Solution

M

Mocha•8/8/23, 3:21 AM

Looks like you're using sqlite. You can:

have a UseRole table
if your project isn't that complex/big, you can just just store it as a string
isAdmin boolean (if that's all you'll need)?

G

gave_oneOP•8/8/23, 4:32 AM

@100xdev @amit13

G

gave_oneOP•8/8/23, 4:32 AM

Error validating model "User": Ambiguous relation detected. The fields

classes

classes

classes

classes and

courses

courses

courses

courses in model

User

User

User

User both refer to

Courses

Courses

Courses

Courses. Please provide different relation names for them by adding `@relation(<name>).

G

gave_oneOP•8/8/23, 4:32 AM

model User {
    id            String    @id @default(cuid())
    name          String?
    email         String?   @unique
    password String? @unique
    emailVerified DateTime?
    image         String?
    admin        Boolean @default(false)
    classes  Courses[]
    courses     Courses  @relation(fields: [coursesId], references: [id]) 
    coursesId String     @unique 
    
    accounts      Account[]
    sessions      Session[]
}
model Courses{
    id String @id @default(cuid())
    name String
    Description String?
    fullMarks Int
    startDate  DateTime
    endDate DateTime
    teacher User?
    user     User  @relation(fields: [UserId], references: [id]) 
    UserId String     @unique 
}

model User {
    id            String    @id @default(cuid())
    name          String?
    email         String?   @unique
    password String? @unique
    emailVerified DateTime?
    image         String?
    admin        Boolean @default(false)
    classes  Courses[]
    courses     Courses  @relation(fields: [coursesId], references: [id]) 
    coursesId String     @unique 
    
    accounts      Account[]
    sessions      Session[]
}
model Courses{
    id String @id @default(cuid())
    name String
    Description String?
    fullMarks Int
    startDate  DateTime
    endDate DateTime
    teacher User?
    user     User  @relation(fields: [UserId], references: [id]) 
    UserId String     @unique 
}

model User {
    id            String    @id @default(cuid())
    name          String?
    email         String?   @unique
    password String? @unique
    emailVerified DateTime?
    image         String?
    admin        Boolean @default(false)
    classes  Courses[]
    courses     Courses  @relation(fields: [coursesId], references: [id]) 
    coursesId String     @unique 
    
    accounts      Account[]
    sessions      Session[]
}
model Courses{
    id String @id @default(cuid())
    name String
    Description String?
    fullMarks Int
    startDate  DateTime
    endDate DateTime
    teacher User?
    user     User  @relation(fields: [UserId], references: [id]) 
    UserId String     @unique 
}

model User {
    id            String    @id @default(cuid())
    name          String?
    email         String?   @unique
    password String? @unique
    emailVerified DateTime?
    image         String?
    admin        Boolean @default(false)
    classes  Courses[]
    courses     Courses  @relation(fields: [coursesId], references: [id]) 
    coursesId String     @unique 
    
    accounts      Account[]
    sessions      Session[]
}
model Courses{
    id String @id @default(cuid())
    name String
    Description String?
    fullMarks Int
    startDate  DateTime
    endDate DateTime
    teacher User?
    user     User  @relation(fields: [UserId], references: [id]) 
    UserId String     @unique 
}

M

Mocha•8/8/23, 4:36 AM

What's the difference between courses and classes? How are you linking User.classes to Courses?

M

Mocha•8/8/23, 4:37 AM

Also note that

coursesId String @unique

coursesId String @unique

coursesId String @unique

coursesId String @unique means two students cannot share one coursesId

G

gave_oneOP•8/8/23, 4:48 AM

each course must have a teacher or instructor
The class in the user is for a student

G

gave_oneOP•8/8/23, 4:50 AM

I have removed the

@unique

@unique

@unique

@unique for both model

G

gave_oneOP•8/8/23, 4:51 AM

@100xdev

G

gave_oneOP•8/8/23, 4:55 AM

I think I will take a different approach instead of me using a relationship system I will just Store the user ID in the course instead

M

Mocha•8/8/23, 5:00 AM

Looks like you have a many-to-many relationship.
One User can have many courses (regardless teacher or student, that could be a userRole or isTeacher column)

G

gave_oneOP•8/8/23, 5:09 AM

so I have to add another model

G

gave_oneOP•8/8/23, 5:17 AM

Screenshot_2023-08-07_at_10.17.50_PM.png

G

gave_oneOP•8/8/23, 5:18 AM

what I did I have one relationship then I just store the ID of the user/teacher end the course

M

Mocha•8/8/23, 5:49 AM

That makes sense for JSON, but for sqlite, I suggest having a separate table for the relationship.
And if a course can only be taught by one teacher, you can have

Courses.teacherId

Courses.teacherId

Courses.teacherId

Courses.teacherId that references the teacher user

Error validating: You defined the enum `UserRole`. But the current connector does not support enums.

Similar Threads

Similar Threads

Similar Threads