This will cause problems with scripts that try to parse the output of the command (which is something I've done).
The ecosystem generally understands what empty tabular output means. For example, a select on an empty table wouldn't try give a special message to create some rows.
I think we already notify people in other places earlier in the process when they don't have a database, like when they log in? I don't think we want to harass people too much, otherwise it might start to feel like an error not to have a database.
turso db list
is not really useful when there are no DBs to be listed.What about telling users to create a database?
Or some nicer message.