Need help in adding Custom Table Names

I donno where I went wrong

LogeshOP•4/23/25, 10:46 PM

✓ Compiled /api/auth/[...all] in 709ms (440 modules)
prisma:query SELECT "public"."User"."id", "public"."User"."name", "public"."User"."email", "public"."User"."createdAt", "public"."User"."updatedAt", "public"."User"."emailVerified", "public"."User"."image" FROM "public"."User" WHERE "public"."User"."email" = $1 LIMIT $2 OFFSET $3
prisma:query INSERT INTO "public"."User" ("id","name","email","createdAt","updatedAt","emailVerified") VALUES ($1,$2,$3,$4,$5,$6) RETURNING "public"."User"."id", "public"."User"."name", "public"."User"."email", "public"."User"."createdAt", "public"."User"."updatedAt", "public"."User"."emailVerified", "public"."User"."image"
prisma:error
Invalid invocation:

{
data: {
accountId: "3BAfEkg1jx9QJtiVGSlYhjzJAm5chngO",
providerId: "credential",
userId: "3BAfEkg1jx9QJtiVGSlYhjzJAm5chngO",
password: "ebd6311b018ef66baac1750c0a4dce1a:a5feb3c830e8b5c2911fad5395c050255b9ed10797f72bd85b47a54ab4f703e35d951dbc580e1930eae709f2d49bd54979a1caaabe6595c68f72986385fd4859",
createdAt: new Date("2025-04-23T22:18:05.596Z"),
updatedAt: new Date("2025-04-23T22:18:05.596Z"),
id: "TlCQJEOM7ZeacFhFwY9s52FE2gXxCPFi",

name: String
},
select: undefined
}

Argument

name

name

is missing.

SERVER_ERROR: PrismaClientValidationError:

Invalid invocation:

{
data: {
accountId: "3BAfEkg1jx9QJtiVGSlYhjzJAm5chngO",
providerId: "credential",
userId: "3BAfEkg1jx9QJtiVGSlYhjzJAm5chngO",
password: "ebd6311b018ef66baac1750c0a4dce1a:a5feb3c830e8b5c2911fad5395c050255b9ed10797f72bd85b47a54ab4f703e35d951dbc580e1930eae709f2d49bd54979a1caaabe6595c68f72986385fd4859",
createdAt: new Date("2025-04-23T22:18:05.596Z"),
updatedAt: new Date("2025-04-23T22:18:05.596Z"),
id: "TlCQJEOM7ZeacFhFwY9s52FE2gXxCPFi",

name: String
},
select: undefined
}

Argument

name

name

is missing.

this is the error I got as it is creating in the account model but not in the AuthAccount model.

schema.prisma6.28KB

Firro•4/23/25, 10:55 PM

Are you calling the account creation yourself or are you using the better-auth signup functionality?

LogeshOP•4/23/25, 11:00 PM

using signup from better-auth.

message.txt4.78KB

Firro•4/23/25, 11:05 PM

Can you embed the relevant part as a message, I can't download stuff right now

Firro•4/23/25, 11:06 PM

Also, importantly: Do you provide a name in the signup function call?

LogeshOP•4/23/25, 11:07 PM

const { data, error: signUpError } = await signUp.email(
{
email,
password,
name,
callbackURL: "/dashboard",
},
{
onError: (ctx) => {
console.error("Error :", ctx.error);
alert(ctx.error.message);
},
}
);

LogeshOP•4/23/25, 11:07 PM

is this okay or do you need something else ?

Firro•4/23/25, 11:08 PM

Mhmm, are you 100% sure name is not empty here?

Firro•4/23/25, 11:08 PM

That's what I'd check first

Firro•4/23/25, 11:09 PM

Ok wait, I just realized, account shouldn't have a name

Firro•4/23/25, 11:09 PM

Can you post the extended schema you did? Only the part for the account

Firro•4/23/25, 11:11 PM

If you only wanted to change the name of the tables, it's surprising that an additional column snuck in

LogeshOP•4/23/25, 11:11 PM

model Account {
id String @id @default(cuid())
userId String
name String
type String
balance Float
currency String @default("USD")
isDefault Boolean @default(false)
creditLimit Float?
dueDate DateTime?
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
accountNumber String?
institution String?
notes String?
isActive Boolean @default(true)
user User @relation(fields: [userId], references: [id], onDelete: Cascade)
transactions Transaction[] @relation("FromAccount")
transfers Transaction[] @relation("ToAccount")
recurringPayments RecurringPayment[]

@@index([userId])
}
this is the account but for this is not for better-auth , I need better-auth to use this model
model AuthAccount {
id String @id @default(cuid())
userId String
accountId String
providerId String
password String?
accessToken String?
refreshToken String?
idToken String?
accessTokenExpiresAt DateTime?
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt

user User @relation(fields: [userId], references: [id], onDelete: Cascade)

@@map("auth_accounts")
}

Firro•4/23/25, 11:12 PM

Have you configured it to via: https://www.better-auth.com/docs/concepts/database#custom-table-names

Database | Better Auth

Learn how to use a database with Better Auth.

LogeshOP•4/23/25, 11:12 PM

yes I tried from this

Firro•4/23/25, 11:13 PM

And then you've ran: ?

Firro•4/23/25, 11:14 PM

Because if so, hmm, tough, don't know why that shouldn't just work then

LogeshOP•4/23/25, 11:14 PM

no I used npx prisma generate

Firro•4/23/25, 11:15 PM

Ahh. Maybe try running the better auth generate command and see what it outputs

LogeshOP•4/23/25, 11:15 PM

let me try as you said

Firro•4/23/25, 11:15 PM

And then compare the two to see what you need to change

Firro•4/23/25, 11:16 PM

In general I'd say you should have a section in your Prisma schema that you just always copy-paste over from the generated better auth schema instead of manually adding the columns

Firro•4/23/25, 11:16 PM

And then the rest of your other application tables below it

LogeshOP•4/23/25, 11:25 PM

didnt work , still stuck with the same error
prisma:error
Invalid invocation:

{
data: {
accountId: "61owOGjhuhqTBQWY79bC51kr9ksQiANd",
providerId: "credential",
userId: "61owOGjhuhqTBQWY79bC51kr9ksQiANd",
password: "84f7e8ce004b0dd3aafe6ee981346a02:1b12c8cbe040aaf3997212ceb4116280a2f84413c0c0d142c93713e4f0b2a823a4a6e473571d31731dc19c7592b03ab48daf7a6bd497d716915f9958715f3ef8",
createdAt: new Date("2025-04-23T23:23:39.386Z"),
updatedAt: new Date("2025-04-23T23:23:39.386Z"),
id: "maorm6FwqdEkngBK7JDDmKfwg4c4ArUc",

name: String
},
select: undefined
}

Argument

name

name

is missing.

Firro•4/23/25, 11:27 PM

Hmm, well, maybe someone else who is more familiar with Prisma+Better Auth could help then, wish you all the best

LogeshOP•4/23/25, 11:27 PM

actually this prisma.account.create() is wrong model and it needs to be prisma.authAccount.create() that is the problem here

Firro•4/23/25, 11:27 PM

Yeah it feels like that, I'd triple check the auth.ts file

Firro•4/23/25, 11:27 PM

But not that familiar with Prisma sorry

FFirro In general I'd say you should have a section in your Prisma schema that you just...

LogeshOP•4/23/25, 11:28 PM

so you are saying we shouldnt disturb better-auth tables and work with other tables for applicaiton logic right ?

Firro•4/23/25, 11:30 PM

Nah, modifying them is 100% the way to go

Firro•4/23/25, 11:31 PM

I did that as well, but for me it just worked

Firro•4/23/25, 11:32 PM

But I'd not manually change them but via changing

auth.ts

auth.ts

-> better-auth/cli generate -> prisma generate -> prisma migrate

Firro•4/23/25, 11:32 PM

So that your auth.ts is the source of truth

Firro•4/23/25, 11:34 PM

Just have to figure out now why it accesses the wrong model

LogeshOP•4/23/25, 11:35 PM

actually I have a table with name Account and I have built applicaiton based on that table, I thought of giving better-auth a try and I coudnt just rename my Account table . so I created another table as required by better-auth . and I couldnt able to point better-auth to use that table as account. Eventhough it was mentioned in docs

LLogesh actually I have a table with name Account and I have built applicaiton based on ...

Faynix•8/29/25, 9:29 PM

Hello, I don't know if you have solved the problem, but I found a solution. In the "Prisma" schema, add "?" like this: "name String? @db.Text" to the user model. Your users are then free to fill in the name field later. Sorry for my bad English, I use a translator.