Hi Senaka, Yes, we can introduce database level collation. We need the documentation updated for create database as follows.
CREATE DATABASE *mybigdb* COLLATE *latin1_general_cs*; thanks Eranda On Sun, Jul 13, 2014 at 4:30 PM, Senaka Fernando <[email protected]> wrote: > Hi Eranda, > > From what I understand the change of collation needs to be done when > creating the database. So, this will mean that we don't have to make any > changes to code/script in the pack but the documentation for MySQL. Can you > confirm? > > Thanks, > Senaka. > > On Sun, Jul 13, 2014 at 8:34 AM, Kasun Gajasinghe <[email protected]> wrote: > >> Hi Eranda, >> >> To which kernel version will this change go to? >> >> Thanks, >> KasunG >> >> >> On Sun, Jul 13, 2014 at 9:42 AM, Eranda Sooriyabandara <[email protected]> >> wrote: >> >>> Hi all, >>> This issue was encountered last Thursday where you can use case >>> insensitive path to retrieve a registry resource on governance mounted. >>> >>> Eg. >>> /_system/governance/A.txt can be retrieve using both >>> >>> 1. /_system/governance/A.txt >>> 2. /_system/governance/a.txt >>> >>> We have go to the code level and saw that this is a cause of retrieving >>> REG_VERSION from the database using the following query. >>> >>> SELECT REG_VERSION FROM REG_RESOURCE WHERE REG_PATH_ID=? AND REG_NAME=? >>> AND REG_TENANT_ID=? >>> >>> So the verdict was that database sending result where its "WHERE" >>> clauses are case insensitive. The scenario was tested on H2 but we see that >>> it works properly where it gives RNF for /_system/governance/a.txt. >>> >>> We further look into this issue and found that this was related to MySQL >>> where we need to specify the COLLATE if we do case insensitive WHERE >>> operations given that the default collation is not case sensitive. >>> So we change the collation to 'latin1_general_cs' from the default " >>> latin1" and it the above usecase worked fine. So we may need to change >>> the registry database scripts to introduce this and may need to create a >>> migration script for the existing databases. >>> >>> Thoughts? >>> >>> thanks >>> Eranda >>> >>> >>> -- >>> >>> *Eranda Sooriyabandara *Senior Software Engineer; >>> Integration Technologies Team; >>> WSO2 Inc.; http://wso2.com >>> Lean . Enterprise . Middleware >>> >>> E-mail: eranda AT wso2.com >>> Mobile: +94 716 472 816 >>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >>> Blog: http://emsooriyabandara.blogspot.com/ >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > > *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* > Software Architect; WSO2 Inc.; http://wso2.com > > > > * Member; Apache Software Foundation; http://apache.org > <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 > 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; > > > *M: +44 782 741 1966 <%2B44%20782%20741%201966> Linked-In: > http://linkedin.com/in/senakafernando > <http://linkedin.com/in/senakafernando>* > Lean . Enterprise . Middleware > -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
