Even if you don’t have a separate db for supertokens, you will still need another table to maintain other user info like bio, avatar etc..

So your code shouldn’t be affected by changing the db for supertokens anyway

It’s just about maintaining isolation which makes it easier to manage

But I’ll create an issue about working with prisma anyway. Thanks!

I mean I guess in this case should I just not worry about interacting with any of the supertokens related data in my app

And just simply - on signing up new user, create a new user in my own personal User db at the same time with the same user ID

Yea. Ideally use the API we provide and that’s it. Should be fine

Yeah that sounds good. Only thing I worry about in the future is maybe emails

In terms of a user changing their email

You recommend attempting to connect to the supertokens db to change the email within emailpassword_users

Or just just not touch that and keep track of the user's email in my own database/table

you could connect to the supertokens db and change the email.. sure.

Yeah but if I do that through Prisma, there's issues with that currently ya

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

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