Prisma•2y ago

Dashboard localhost:4467/_admin after run command: yarn prisma:deploy-force all table is 0

why in the prism dashboard there are only 2 tables that have data yaoit PageAccess 80 the data does not match the data in postgres, this is when running: yarn prisma:deploy-force
prisma version 1.32

JTB•6/25/24, 6:08 AM

You're showing us two different tables. Depending on the scheme, you can also put together tables that are dependent on each other.

arga fauziantoOP•6/25/24, 8:59 AM

@JTBYes, why is the schema on the left not the same as the schema in Postgres?

JTB•6/25/24, 9:01 AM

idk what you declated on prisma.schema?

arga fauziantoOP•6/25/24, 9:03 AM

like the picture below
@JTB

arga fauziantoOP•6/25/24, 9:04 AM

@JTB I'm a little confused, how do I make the schema contents the same as in Postgres?

arga fauziantoOP•6/25/24, 9:08 AM

@JTB Do you have any suggestions for the above problem?

JTB•6/25/24, 9:11 AM

Without knowing your complete schema.prisma, nobody will be able to tell you anything. You can make certain joints in your schema that are displayed in the studio but not in the database.

arga fauziantoOP•6/25/24, 9:18 AM

@JTBbut when you try the production URL, it works, for example if you want to retrieve a user's login, all the data appears

JTB•6/25/24, 9:22 AM

and? that doesn't contradict any of my explanations.

JTB•6/25/24, 9:23 AM

arga fauziantoOP•6/25/24, 9:23 AM

@JTB prisma.schema contains just that, why is it 0 data which is confusing when running it to do local development

JTB•6/25/24, 9:25 AM

I don't know how I can explain it any more simply. If you declare connections in the schema that do not physically exist, like a virtualisation of the table, no new tables are created in the database but you virtualise them. But whether this is the case and WHAT exactly is the case with you cannot be said on the basis of the screen shorts.