ansible/database
Alan Fairless 927a30c404 Fix postgresql_user to understand PG namespaces
Previously postgresql_user quoted user supplied identifers to create
grant statements that look like this:

    GRANT SELECT on "tablename" to "user";

Which only works if the tablename is not in a namespace.  If you supply
a namespaced tabelname like "report.revenue" then it creates this
incorrect statement:

    GRANT SELECT on "report.revenue" to "user";

Which will not find the "revenue" table in the "report" namespace, but
will rather look for a table named "report.revenue" in the current
(default public) namespace.  The correct form is:

    GRANT SELECT on "report"."revenue" to "user";

This approach could have the unfortunate effect that code that
previously relied on the other behavior to grant privileges on tables
with periods in their names may now break.  PostgreSQL users
typically shouldn't name tables as such, and users can still access the
old behavior and use tablenames with periods in the if they must by
supplying their own quoting.
2014-01-04 15:37:08 -06:00
..
mongodb_user Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00
mysql_db Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00
mysql_replication Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00
mysql_user Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00
mysql_variables Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00
postgresql_db Merge pull request #5099 from tartansandal/postgresql_db_check_mode 2013-12-16 11:39:16 -08:00
postgresql_privs Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00
postgresql_user Fix postgresql_user to understand PG namespaces 2014-01-04 15:37:08 -06:00
redis Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00
riak Addresses #5023 Fix import comments 2013-12-02 15:13:49 -05:00