On 02/24/2016 02:34 PM, Sean Dague wrote:
There are no urls stored here. This is content coming through the body.
While I do appreciate many folks weighing in that haven't read the bug
yet, I would be even better if people did read the bug first.
We have the ability to decide at the API level what the behavior is of
payloads in POST / GET. Given the majority of our users are on mysql,
they've never had access to case sensitive overlapping metadata on
aggregates before. Doing so seems odd and potentially confusing.
On the other hand, coming from a UNIX environment where case sensitivity is the
default, it seems odd that we'd intentionally become case-insensitive.
For option 2 do we need to actually update the DB column description? Or is
there a way to alter the query to be case-insensitive without altering the
column itself (using collate maybe)?
Chris
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
