Dnhatsave
commented
6 years ago hey there, i had the same problem in some tables using a MySql workbench 6.3. to solve this issue i've to disable the foreign key checks with this query SET GLOBAL FOREIGN_KEY_CHECKS=0;
for some reason mysql prevented the execution of this query, probably because of the version or my configurations.
I hope this is useful.
best regards.
fcorti
hello,
I think this is a bug: when retrieving the tasks from Alfresco, Alflytics is expecting to get an assignee for every task, but some tasks may have no assignee in a specific time, for instance, when a task is sent to a group and no one accepted it yet.
This is the error:
2017-09-18 15:57:54,684 ERROR [org.pentaho.di] 2017/09/18 15:57:54 - Execute row SQL script.0 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : Error in step, asking everyone to stop because of: 2017/09/18 15:57:54 - Execute row SQL script.0 - Couldn't execute SQL: INSERT INTO "OPE_ALF_WF_TASKS"("INSTANCE_ID","ID","WF_INSTANCE_ID","NAME","DESCRIPTION","STARTED_AT","DUE_AT","ASSIGNEE","STATE","PRIORITY","TASK_DEFINITION_ID") VALUES (1,'50505','49571','Description','My title 3213',TO_DATE('2017-09-12T16:20:44.466+0000', 'YYYY-MM-DD"T"HH24:MI:SS.FFF'),null,null,'unclaimed',2,'alfrescoUsertask5') 2017/09/18 15:57:54 - Execute row SQL script.0 - 2017/09/18 15:57:54 - Execute row SQL script.0 - integrity constraint violation: NOT NULL check constraint; SYS_CT_10677 table: "OPE_ALF_WF_TASKS" column: ASSIGNEE
So, it seems the column restrinction should be eliminated.
thank you!