betanummeric

@tchernomax FYI, in case you lock yourself out of a mysql/mariadb you can recover by restarting it with `--skip-grant-tables --skip-networking`, connect from localhost and update the `mysql.user` or `mysql.global_priv` table,...

For comparison, the [`community.mysql.mysql_user` module](https://docs.ansible.com/ansible/latest/collections/community/mysql/mysql_user_module.html) has one option `priv` to specify privileges on objects. The module has three ways of handling these: - replacing (default): grant the specified privileges, revoke...

We can change independently how to specify - what objects shall be acted on - what privileges shall be acted on - how those things shall be treated (scope of...

The particular issue can probably solved quite easily by giving the compressed file on stdin to the uncompressor, instead of a command line argument. This should be tested carefully with...

Hi @munnik Although not really intended, it should be possible to simply write multiple statements as one "query": ```yaml - community.postgresql.postgresql_query: login_user: "somebody" login_password: "pw" login_host: "pghost" db: "something" query:...

We should implement proper quote parsing, the `ldapbindpasswd` is not the only value that can contain arbitrary characters. The existing implementation of using `'#' in line` is pretty naive.

The postgresql collection comes with [some parsing magic](https://github.com/ansible-collections/community.postgresql/blob/639197ead257c1b4c63627d035996790e904cf6e/plugins/module_utils/database.py#L39-L128) to detect if the identifier (e.g. schema name) is already quoted, and add quotes if necessary. While the parsing could be improved,...

@peterkrawiec1 What version of the community.postgresql collection are you using? Version 2.3.2 includes #382 which hopefully already fixes your issue.

uhh, this PR is quite old already. But I think it is still justified. The change size categorization mostly depends on whether we call the existing behavior a bug or...