Rowan

Hi @zeryx , Thanks for responding. I hope i'm not misinterpreting what we're discussing here, I think there might be some crossed wires. This won't interfere with the current timeout...

I have a couple of ideas for solving the signatures problem, but they involve specifying the types on the arguments, which might be a breaking change from here on out.

I could definitely do with some attention on that PR, there are a few bits where I don't understand the authorial intent. Happy to help though!

There's definitely more context about what options can/should be passed via config file. Maybe we should keep this limited to username/password for now? https://tomlankhorst.nl/mysql-my-cnf-options-file/

Postgres support, integration tests have now been added!

An Update on this one. to tie in with #31 I think that things like the progressbar updates should be uplifted to `cli.py`, and this would be a good solution...

Sounds logical. do you know if this behaviour is similar across the other supported DBs (i.e. postgres, mssql)? I'm just thinking about how best to support this.

Hi @balcsida ! Late news, but this feature was released in v1.24.0. for MySQL & postgres, you should be able to use the CLI's respective config files to pass credentials...

I feel i have to start this reply off by saying that I feel anonymization is a fundamentally manual process and must always have some human oversight, especially where schema...

No worries - as i said, I think that generation/initial strategyfile tooling is a good idea, but i'm not sure i see the use-case for the "pickup any schema changes...