`wasp db reset --seed` command

[zkmrtn8]

A new CLI command that would reset and then re-seed the database all at once, preventing the need to build the project twice (which takes quite a while!).

[Martinsos]

@zkmrtn8 why would you need to build the project twice otherwise? How do you do this at the moment? I would expect you can just do wasp db reset && wasp seed <seed-name> (maybe I am out of touch though, haven't done it recently)?

[zkmrtn8]

As noted in #2202, in order to run any commands on the DB it compiles/builds the whole project, even if the actual code hasn't changed. It doesn't really need to do this even once for most db commands (as far as I can think of, anyways), so it seems like they could be combined. In other words, right now it does this:

• wasp db reset
  • Compile project, check for type errors, etc. (takes a minute or two)
  • Reset database
  • Apply migrations
• wasp db seed
  • Compile project, check for type errors, etc.
  • Run seed

but it could instead combine the build step:

• wasp db reset --seed <seed-name>
  • Compile project, check for type errors, etc. (takes a minute or two)
  • Reset database
  • Apply migrations
  • Run seed

[Martinsos]

Ok got it @zkmrtn8 !

Ideally solution would be to reduce that compilation time and to not compile the whole project where it doesn't need to, and combining two commands into one to combat that is really a fix of a symptom, not of the cause. Doesn't mean it might not be helpful do to it still.

One thing I am curious about is that compilation of the TS project takes so long for you, a minute or two. Is your project unusually big, I would assume probably not? Are you maybe running on WSL, and if so, are your files on Windows file system or Linux file system? Anything else that might be peculiar for your project?

[zkmrtn8]

Might be more of my impatience that makes it seem like it takes that long 🙃 I just timed it and it's only 20-30 seconds, though that does add up when making a lot of schema changes and needing to reset » migrate » seed every time.

[Martinsos]

Might be more of my impatience that makes it seem like it takes that long 🙃 I just timed it and it's only 20-30 seconds, though that does add up when making a lot of schema changes and needing to reset » migrate » seed every time.

That also sounds like a lot to me though! We will check the times on our side for sure, but as for the question above: are you on WSL, and if so is it Win or Linux file system that your Wasp project source files are on? This is often the culprit, so that is why I am asking.

[zkmrtn8]

I'm on an M4 Pro Macbook Pro. Looks like the main thing that takes a while is Building SDK and Setting up Database (perhaps it's a Neon issue?)

[Martinsos]

I'm on an M4 Pro Macbook Pro. Looks like the main thing that takes a while is Building SDK and Setting up Database (perhaps it's a Neon issue?)

Ok great, this is help us to reproduce it. Might be Neon but I don't know yet.

Let's leave the issue open, we will triage it on the next sprint planning!