Doug Stevenson

I will add that the response needs to be unambiguously clear (with something like an error code rather than an error message string meant for humans) that this rollback happened,...

To be more specific: ``` # Create db file $ sqlite3 test.db # Try to get sqld to use the file directly $ turso dev --db-file test.db ... Error: failed...

The case for importing a sqlite db to a "managed" directory rather than using one in-place is even stronger now, given sqld instances configured to use the new namespaced directory...

Dump and load is mentioned in the [reference documentation](https://docs.turso.tech/reference/turso-cli#database-dump-and-load). And yes, we can definitely do better as @penberg says.

Could you say more about what you perceive to be the problem here? This is actually fewer lines of output than the output of `db create` itself.

OK, so it sounds like you're proposing two things. The first is the message that introduces the command (it should just say "to get a connection URL"), and also the...

If you really want to speed this up, why not just print the URL in the `db create` output instead of making them run a command? I think the original...

There's a balance here between being fast and being generally helpful. I'll point out that the use case you're optimizing for isn't helped by `db shell` in the output. However,...

This was one of my recommendations from last week as an option *instead of* using the CLI flag, but I don't see a reason not to offer it *in addition...

This was filed back when there were other problems with Turso that made connections hang indefinitely. I'm not sure about the best repro now, but you might be able to...