Gerhard

Will you ever have an interest to try this command?

Will you ever have an interest to try this command?

Not just that, it also configures your app. It starts your app with that Neon branch. So there's no more manual, it's like one command and it will run everything. It will create the branch and then it will configure your app to use the branch. There's no more manual dicking around and you can believe this.

Not just that, it also configures your app. It starts your app with that Neon branch. So there's no more manual, it's like one command and it will run everything. It will create the branch and then it will configure your app to use the branch. There's no more manual dicking around and you can believe this.

Yeah, I haven't looked into that. It does make sense. It does make sense to add it, by the way. And even if the CLI doesn't support it, maybe there's a curl request that we can do to the API to get this synced. But that makes sense.

Yeah, I haven't looked into that. It does make sense. It does make sense to add it, by the way. And even if the CLI doesn't support it, maybe there's a curl request that we can do to the API to get this synced. But that makes sense.

Right. So the freshens ones, to get the freshens ones, which is a great idea, by the way, the first command will take longer because it has to pull down the entire database. And that takes a while. And then it has to load the entire database. It basically removes what you have locally and it just reports everything.

Right. So the freshens ones, to get the freshens ones, which is a great idea, by the way, the first command will take longer because it has to pull down the entire database. And that takes a while. And then it has to load the entire database. It basically removes what you have locally and it just reports everything.

So that can take up to five minutes depending on internet connection, a bunch of things.

So that can take up to five minutes depending on internet connection, a bunch of things.

That's why the command now handles all of that, so that you don't have to worry, did I set the correct environment variables? Is everything correct? And because everything happens inside of the command, once it gets to a point, like we had, for example, Adam's

That's why the command now handles all of that, so that you don't have to worry, did I set the correct environment variables? Is everything correct? And because everything happens inside of the command, once it gets to a point, like we had, for example, Adam's

case where you know sometimes it fails and then you don't like what state am i in this command tends to be self-contained in the point what that means is that once it gets to a certain point you're safe you're sure it will continue and it will finish it will do the right thing and it's all embedded in the actual command

case where you know sometimes it fails and then you don't like what state am i in this command tends to be self-contained in the point what that means is that once it gets to a certain point you're safe you're sure it will continue and it will finish it will do the right thing and it's all embedded in the actual command

Now, this command, when you're connected to a remote database, it can be slightly slower. So for me, for example, I preferred downloading all the data locally and having all of that locally because it felt snappier. And even though the query planner, we warm up the query planner so that things are cached, we do a couple of things like that, it still feels slower.

Now, this command, when you're connected to a remote database, it can be slightly slower. So for me, for example, I preferred downloading all the data locally and having all of that locally because it felt snappier. And even though the query planner, we warm up the query planner so that things are cached, we do a couple of things like that, it still feels slower.

It still is slower because it has to do all those round trips, right? And they're all remote. They're all remote calls to this remote database. So I think the choices between paying the penalty once, five minutes, three minutes, depending on your internet connection to load all the data, and then you know you have the latest, or...

It still is slower because it has to do all those round trips, right? And they're all remote. They're all remote calls to this remote database. So I think the choices between paying the penalty once, five minutes, three minutes, depending on your internet connection to load all the data, and then you know you have the latest, or...

Pay a little bit of penalty every time you load the page because it may take, I don't know, a second slower sometimes, depending on how many queries you're running. So both options are there. I think knowing Adam, I think he would prefer the second option so that he's connected against a remote database. And I think you would prefer the first option. So we have a mix of both.

Pay a little bit of penalty every time you load the page because it may take, I don't know, a second slower sometimes, depending on how many queries you're running. So both options are there. I think knowing Adam, I think he would prefer the second option so that he's connected against a remote database. And I think you would prefer the first option. So we have a mix of both.