Setup script runs db seed script twice when using sqlite. about indie-stack

[earlofurl]

Discord user cev#2144 says that the setup command works as intended when using postgresql, but runs twice when using sqlite.

It is unclear from the Prisma Docs which behavior is intended.

migrate dev says it will generate artifacts, but does not say it's supposed to run the seed command.
The next section, migrate reset, does explicitly state that it runs the seed command.

In my case, using sqlite, the problem is effectively fixed by replacing "setup": "prisma migrate dev" && prisma db seed with "setup": "prisma migrate dev"

However, it sounds like this would not automatically seed the db for users who switch to postgresql.

[mcansh]

this doesn't appear to happen in prisma 3.15.2

nope never mind it does, we can update this script as seeding is ran during prisma migrate dev https://github.com/prisma/prisma/blob/main/packages/migrate/src/commands/MigrateDev.ts#L325

plus we ship a migration in this template so really we should be using prisma migrate deploy