[jboss-jira] [JBoss JIRA] Resolved: (JBRULES-2325) Drools Flow BAM Module(5.1.0.M1) - Primary Key of String type creating problem

[Kris Verlaenen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBRULES-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kris Verlaenen resolved JBRULES-2325.
-------------------------------------

    Fix Version/s: 5.1.0.M2
       Resolution: Duplicate Issue
         Assignee: Kris Verlaenen  (was: Mark Proctor)


Duplicate of JBRULES-2291

> Drools Flow BAM Module(5.1.0.M1) - Primary Key of String type creating problem
> ------------------------------------------------------------------------------
>
>                 Key: JBRULES-2325
>                 URL: https://jira.jboss.org/jira/browse/JBRULES-2325
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-process
>    Affects Versions: 5.1.0.M1
>         Environment: Java 5, Drools 5.1.0.M1, MySQL 5.1
>            Reporter: vijpan
>            Assignee: Kris Verlaenen
>             Fix For: 5.1.0.M2
>
>
> I am planning to use Drools Flow BAM (5.1.0.M1) module to store the processes instances for audit purpose. I generated the DDL with the help of Hibernate Tools against the MYSQL 5.1(INNODB) 
> DDL for the 2 tables are given below -- the interesting part is the "id" column as "varchar" ---- this gives error when we try to execute the DDL against the mysql. 
>    create table AUDIT_NODE_INSTANCE_LOG (
>         id varchar(255) not null auto_increment,
>         type integer,
>         nodeInstanceId varchar(255),
>         nodeId varchar(255),
>         processInstanceId bigint,
>         processId varchar(255),
>         DATE datetime,
>         primary key (id)
>     ) ENGINE=InnoDB;
>      create table AUDIT_PROCESS_INSTANCE_LOG (
>         id varchar(255) not null auto_increment,
>         processInstanceId bigint,
>         processId varchar(255),
>         START_DATE datetime,
>         END_DATE datetime,
>         primary key (id)
>     ) ENGINE=InnoDB;
>  The error we get is 
> Error: Incorrect column specifier for column 'id'
> SQLState:  42000
> ErrorCode: 1063
> Just to test with different column name such as "primaryid" - we still the same error.
> If i change the column type to "bigint" - the tables get created fine. 
> I think with the "native" strategy - the column type should be changed from 'String' to 'long' 
> Thanks
> Vijay
> p.s. I used a naming strategy for the hibernate that's why the above table names.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira