Hi, do you have mysql setup with innoDB engine, it's know problem of myISAM El 09/04/2015 07:38, "Dan Haywood" <[email protected]> escribió:
> Jeroen and I discussed this topic offlist yesterday, and came to the > conclusion that we probably ought to keep issues relating to the addons > outside of the ASF JIRA. > > The ASF board have already asked us to make it clear that the Isis addons > are not under the governance of ASF (which we have done by clearly updating > our website throughout); having issues in the Isis (ASF) JIRA that relate > to those addons might suggest otherwise. > > Accordingly, I've updated the Isis JIRA and got rid of the (little used) > "Addons" components, and closed any currently open tickets relating to > addons (only a handful) and created corresponding tickets in the relevant > github repo for the various addons. > > ~~~ > > The above notwithstanding, if anyone has questions related to the use of > the Isis addons, do please continue to post them here. > > Cheers > Dan > > > > > > On 7 April 2015 at 20:34, Jeroen van der Wal <[email protected]> wrote: > > > Hi Martin, > > > > You got me confused: our ASF JIRA project has labels for each of the > > components so issues can be filed there too. Perhaps we should make a > > decision on where we register the issues and make that clear in the > setup. > > > > From a purist point of view the issues should reside at their respective > > github repositories. In practice that shatters the backlog across many > > locations. I'm biased to a practical solution and have a single JIRA > > project. Alternatively we could set up a second JIRA project solely for > > Isis addons. > > > > What do you (and others!) think? > > > > Cheers, > > > > Jeroen > > > > > > [1] > > > > > https://issues.apache.org/jira/browse/ISIS/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel > > > > On 7 April 2015 at 20:17, Martin Grigorov <[email protected]> wrote: > > > > > Hi, > > > > > > AuditEntry [1] is part of IsisAddons so maybe the ticket should be > filed > > at > > > https://github.com/isisaddons/isis-module-audit/issues > > > > > > > > > 1. > > > > > > > > > https://github.com/isisaddons/isis-module-audit/blob/e7687b186497a620aa8e1a68b93ede93f81d55cd/dom/src/main/java/org/isisaddons/module/audit/dom/AuditEntry.java#L112 > > > > > > Martin Grigorov > > > Freelancer, available for hire! > > > Wicket Training and Consulting > > > https://twitter.com/mtgrigorov > > > > > > On Tue, Apr 7, 2015 at 6:25 PM, Jeroen van der Wal < > [email protected]> > > > wrote: > > > > > > > Hi James, > > > > > > > > We're using PostgreSQL and MS SQL Server in our productions > > environments > > > so > > > > we've never encountered this. > > > > > > > > If your application doesn't need the audit module you can comment out > > the > > > > dependency on isis-module-audit in pom.xml. Otherwise you need to > clone > > > the > > > > isis-module-audit and remove the index from the AuditEntry class. > > > > > > > > Could you raise a ticket in JIRA [1]? > > > > > > > > Cheers, > > > > > > > > > > > > Jeroen > > > > > > > > [1] https://issues.apache.org/jira/browse/ISIS > > > > > > > > > > > > > > > > On 5 April 2015 at 08:53, [email protected] <[email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi,I have encountered an error when i run todoapp with mysql.Error > > > > message > > > > > is : Specified key was too long; max key length is 767 bytes.Then > I > > > > trace > > > > > into source and find auditentry class will create a unique index > > with > > > > > transactionid,target and propertyid,but field target type is > > > > varchar(2000) > > > > > , it is too long to be an index. > > > > > so ,how can i ewsolve it? > > > > > Thanks ! > > > > > James > > > > > > > > > > > > > > > > > > > >
