Not sure I would think that a migrate patch is the right approach here... I kind of feel like this is a DBA or sysops responsibility.
Thoughts? -jay On Tue, Jan 10, 2012 at 4:43 PM, Nachi Ueno <[email protected]> wrote: > Hi Jay > > Thanks > Is it possible to do it on sqlalchemy.migration ? > > > 2012/1/10 Jay Pipes <[email protected]>: >> +1 for Case Sensitive. For MySQL, this is a configuration issue. The >> default character set and collation should use the *_cs variants. For >> existing MySQL installations, an ALTER TABLE ... MODIFY COLUMN ... >> CHARACTER SET ... COLLATION ... *_cs would need to be done for >> affected tables. >> >> -jay >> >> On Tue, Jan 10, 2012 at 4:15 PM, Nachi Ueno >> <[email protected]> wrote: >>> Hi folks >>> >>> Nova,Keystone,Glance uses RDBMS and they use unique key constraints. >>> Nowadays, we can use Mysql,Sqlite,Postgresql. >>> Unfortunately, the unique key behaviors of each DB are different. >>> >>> - Mysql : case-insensitive >>> - Sqlite : case-sensitive >>> - Postgresql : case-sensitive >>> >>> I wanna know the spec of OpenStack. >>> Unique key is case-sensitive or *in*sensitive? >>> >>> Cheers >>> Nati >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
