pgsql trove database create fails silently when collate or character_set options are used
Bug #1513150 reported by
Alex Tomic
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Confirmed
|
Undecided
|
Doug Shelley | ||
Bug Description
Pgsql has different collation/encoding names than mysql. If we pass in a mysql-specific collation / encoding, the pgsql guest will fail, while attempting to pass a pgsql-specific name will fail validation in the API layer, never making it to the guest.
| Changed in trove: | |
| assignee: | nobody → Alex Tomic (atomic777) |
| Changed in trove: | |
| assignee: | Alex Tomic (atomic777) → Doug Shelley (0-doug) |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on trove (master) | #1 |
To post a comment you must log in.
Change abandoned by Masaki Matsushita (<email address hidden>) on branch: master
Review: https:/