Ok I guess the migration stores it different in th...
# orm-help
m
Ok I guess the migration stores it different in the DB? The client gets the data just fine
a
I haven’t had any issues with migrations personally. It feels like the software is production ready to me.
m
Have you tried playing in your SQL shell?
A standard SELECT query yields the wrong results but using the PrismaClient works fine
I mean migrations are experimental for a reason so my guess is they aren't working 100%
r
@Malik I think you’re issue is different as there’s no difference in where Migrate stores the migrations or Studio stores the data. It’s in the same places as how you’ve defined your database URL in your
schema.prisma
. It would be great if you could open an issue here with all the reproduction steps.