Jelte Fennema-Nio
Jelte Fennema-Nio
Moved this to the 0.2.0 milestone, to allow us to focus on stability testing for 0.1.0. We might still merge part of this PR for 0.1.0 where necessary to resolve...
Closing this in favor of all the smaller PRs that we've been doing to address this problem step-by-step
Re-opening for tracking, since I created a #876 that fixes this. My main usecase for allowing replication connections is giving users only a single connection string, that works for everything.
FYI it seems that's because `NUMERIC` without a size is downgraded to a double in duckdb. I'm wondering if that's what we actually want to do.
@rcronin yes, it would. This would fall under situation number 3 (the ones we should solve the first). For now as a workaround you can use DuckDB its `strftime` and...
Yeah this is still pending
I think including milliseconds definitely makes a lot of sense, even at the slight risk of breaking someone. And I understand why you want the now timestamp, but it does...
How about we start supporting commands like the following. So users can customize what they want returned. ``` SHOW POOLS INCLUDE_TIMESTAMP; SHOW USERS INCLUDE_TIMESTAMP; ```
I'm fine with that option style. I don't think we need a big parser for this. If we only support string arguments and don't allow spaces in tokens, then we...
As described in another design document eventually I want to add support for multiple databases (after we support a single MotherDuck database). That would require us to translate schema names...