[ 
https://issues.apache.org/jira/browse/AIRAVATA-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Christie reopened AIRAVATA-2309:
---------------------------------------

[~scnakandala],

I'm still getting the error. The setting you changes doesn't seem to affect the 
character set of the created table. For example, one of the tables that is 
created is the DOMAIN table and here's what MySQL shows for the CREATE statement
{noformat}
MariaDB [sharing_catalog]> show create table domain;
+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table  | Create Table                                                         
                                                                                
                                                                                
                                                |
+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| domain | CREATE TABLE `domain` (
  `DOMAIN_ID` varchar(255) NOT NULL,
  `NAME` varchar(255) NOT NULL,
  `DESCRIPTION` varchar(255) DEFAULT NULL,
  `CREATED_TIME` bigint(20) NOT NULL,
  `UPDATED_TIME` bigint(20) NOT NULL,
  PRIMARY KEY (`DOMAIN_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 |
+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
{noformat}

Maybe specify the charset on the CREATE TABLE statement?

> SHARING table: MySQL complains "Specified key was too long; max key length is 
> 3072 bytes"
> -----------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2309
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2309
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Assignee: Supun Chathuranga Nakandala
>
> Error occurs while trying to create the SHARING table:
> {code:sql}
> CREATE TABLE SHARING (
>   PERMISSION_TYPE_ID VARCHAR(255) NOT NULL,
>   ENTITY_ID VARCHAR(255) NOT NULL,
>   GROUP_ID VARCHAR(255) NOT NULL,
>   SHARING_TYPE VARCHAR(255) NOT NULL,
>   INHERITED_PARENT_ID VARCHAR(255),
>   CREATED_TIME BIGINT NOT NULL,
>   UPDATED_TIME BIGINT NOT NULL,
>   PRIMARY KEY (PERMISSION_TYPE_ID, ENTITY_ID, GROUP_ID, INHERITED_PARENT_ID),
>   FOREIGN KEY (PERMISSION_TYPE_ID) REFERENCES 
> PERMISSION_TYPE(PERMISSION_TYPE_ID) ON DELETE CASCADE ON UPDATE CASCADE,
>   FOREIGN KEY (INHERITED_PARENT_ID) REFERENCES ENTITY(ENTITY_ID) ON DELETE 
> CASCADE ON UPDATE CASCADE,
>   FOREIGN KEY (GROUP_ID) REFERENCES USER_GROUP(GROUP_ID) ON DELETE CASCADE ON 
> UPDATE CASCADE
> );
> {code}
> This key is fine in the dev database on gw62.  I think the reason it fails 
> for me is that my databases have a default encoding of UTF-8. On gw62 the 
> encoding is latin1_swedish_ci.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to