yea true. So you will have to query it manually

It's strange that's happening

yea it is.. will investigate the issue at some point

Unless something looks wrong here in terms of the generated introspection

Let me take a look again

cool. Lmk. I have created an issue for now: https://github.com/supertokens/supertokens-core/issues/152

Feel free to comment in the above

@User I posted in the github issue the exact migration file that Prisma Migrate is creating

Let me know if anything looks like it was generated incorrectly

Thanks

message has been deleted

error still coming?

Yeah do you think you could look over the migration file Prisma created. Maybe one of the types is wrong?

yea. you are right

time_joined

should be

BIGINT UNSIGNED NOT NULL

not

INTEGER

same for

created_at_time

in

session_info

table

and for

expires_at

in

session_info

and for

created_at_time

in

key_value

You can see the desired table structure here: https://supertokens.io/docs/emailpassword/quick-setup/database-setup/mysql (scroll down and click on "See table structure")

and compare with what prisma generated

i believe, correcting those should sort this issue out!

kk let me modify this migration file and see what happens

Okay it's 100% something related to bigint

yea.

are you using postgres or mysql?

I have an idea