topic possible bug concerning PostgreSQL in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71647#M46423 <HTML><HEAD></HEAD><BODY><SPAN>hi,</SPAN><BR /><BR /><SPAN>i may found a bug concerning PostgreSQL and HistoricDetailQuery / VariableUpdates</SPAN><BR /><BLOCKQUOTE class="jive-quote">histsvc.createHistoricDetailQuery().processInstanceId(task.getProcessInstanceId()).variableUpdates().list()</BLOCKQUOTE><BR /><BR /><SPAN>Exception:</SPAN><BR /><BLOCKQUOTE class="jive-quote">### Cause: java.lang.IllegalArgumentException: Mapped Statements collection does not contain value for org.activiti.engine.impl.persistence.entity.HistoricDetailEntity.selectByteArrayById_postgres<BR />&gt;&gt;java.lang.IllegalArgumentException: Mapped Statements collection does not contain value for org.activiti.engine.impl.persistence.entity.HistoricDetailEntity.selectByteArrayById_postgres<BR />&gt;&gt;&nbsp;&nbsp;&nbsp;at org.apache.ibatis.session.Configuration$StrictMap.get(Configuration.java:462)</BLOCKQUOTE><BR /><SPAN>the SELECT Statement "selectByteArray_postgres" does not exist in VariableInstance.xml</SPAN><BR /><BR /><SPAN>there is only "selectByteArray_postgres" and "selectByteArray". </SPAN><BR /><BR /><SPAN>so i changed HistoricDetail.xml</SPAN><BR /><PRE class="language-none line-numbers"><CODE><BR />Index: HistoricDetail.xml<BR />===================================================================<BR />— HistoricDetail.xml&nbsp;&nbsp;&nbsp;(revision 2770)<BR />+++ HistoricDetail.xml&nbsp;&nbsp;&nbsp;(working copy)<BR />@@ -118,7 +118,7 @@<BR />&nbsp;&nbsp;&nbsp;&nbsp; &lt;association property="byteArrayValue" <BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; column="BYTEARRAY_ID_" <BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; javaType="org.activiti.engine.impl.persistence.entity.ByteArrayEntity" <BR />-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; select="selectByteArrayById_postgres" /&gt;<BR />+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; select="selectByteArray" /&gt;<BR />&nbsp;&nbsp; &lt;/resultMap&gt;<BR /> <BR />&nbsp;&nbsp; &lt;resultMap id="historicFormPropertyResultMap" extends="historicDetailResultMap" type="org.activiti.engine.impl.persistence.entity.HistoricFormPropertyEntity"&gt;<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>may the whole seperation of mappings for postgre is obsolete</SPAN><BR /><BLOCKQUOTE class="jive-quote">&lt;resultMap id="historicVariableUpdateResultMap_postgres" extends="historicDetailResultMap" type="org.activiti.engine.impl.persistence.entity.HistoricVariableUpdateEntity"&gt;</BLOCKQUOTE><BR /><SPAN>and</SPAN><BR /><BR /><BLOCKQUOTE class="jive-quote">&lt;resultMap id="historicDetailResultMap_postgres" type="org.activiti.engine.impl.persistence.entity.HistoricDetailEntity"&gt;</BLOCKQUOTE><BR /><SPAN>because differentiation for postgres is done in "DbSqlSessionFactory.java"</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />public class DbSqlSessionFactory implements SessionFactory {<BR /><BR />&nbsp; protected static final Map&lt;String, Map&lt;String, String&gt;&gt; databaseSpecificStatements = new HashMap&lt;String, Map&lt;String,String&gt;&gt;();<BR /><BR />&nbsp; static {<BR />&nbsp;&nbsp;&nbsp;&nbsp; //mysql specific&nbsp; <BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("mysql", "selectNextJobsToExecute", "selectNextJobsToExecute_mysql");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("mysql", "selectProcessDefinitionsByQueryCriteria", "selectProcessDefinitionsByQueryCriteria_mysql");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("mysql", "selectProcessDefinitionCountByQueryCriteria", "selectProcessDefinitionCountByQueryCriteria_mysql");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("mysql", "selectDeploymentsByQueryCriteria", "selectDeploymentsByQueryCriteria_mysql");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("mysql", "selectDeploymentCountByQueryCriteria", "selectDeploymentCountByQueryCriteria_mysql");<BR />&nbsp;&nbsp;&nbsp; <BR />&nbsp;&nbsp;&nbsp; //postgres specific<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "insertByteArray", "insertByteArray_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "updateByteArray", "updateByteArray_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectByteArray", "selectByteArray_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectResourceByDeploymentIdAndResourceName", "selectResourceByDeploymentIdAndResourceName_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectResourcesByDeploymentId", "selectResourcesByDeploymentId_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectHistoricDetailsByQueryCriteria", "selectHistoricDetailsByQueryCriteria_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "insertIdentityInfo", "insertIdentityInfo_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "updateIdentityInfo", "updateIdentityInfo_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectIdentityInfoById", "selectIdentityInfoById_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectIdentityInfoByUserIdAndKey", "selectIdentityInfoByUserIdAndKey_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectIdentityInfoByUserId", "selectIdentityInfoByUserId_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectIdentityInfoDetails", "selectIdentityInfoDetails_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "insertComment", "insertComment_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectCommentsByTaskId", "selectCommentsByTaskId_postgres");<BR />&nbsp;&nbsp;&nbsp; addDatabaseSpecificStatement("postgres", "selectCommentsByProcessInstanceId", "selectCommentsByProcessInstanceId_postgres");<BR />…<BR />…<BR />…<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>after applying the above patch, the query is working. I haven´t tested the patch against the testsuite.</SPAN><BR /><BR /><SPAN>I´´m working with activiti-engine 5.5 but in 5.6 relevant code isn´t changed.</SPAN><BR /><BR /><SPAN>kind regards</SPAN><BR /><SPAN>philipp eichhorn</SPAN></BODY></HTML> Thu, 16 Jun 2011 13:37:36 GMT pcsquirrel 2011-06-16T13:37:36Z possible bug concerning PostgreSQL https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71647#M46423 hi,i may found a bug concerning PostgreSQL and HistoricDetailQuery / VariableUpdateshistsvc.createHistoricDetailQuery().processInstanceId(task.getProcessInstanceId()).variableUpdates().list()Exception:### Cause: java.lang.IllegalArgumentException: Mapped Statements collection does not contain value Thu, 16 Jun 2011 13:37:36 GMT https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71647#M46423 pcsquirrel 2011-06-16T13:37:36Z Re: possible bug concerning PostgreSQL https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71648#M46424 <HTML><HEAD></HEAD><BODY><SPAN>In rev. 2768, i changed "selectByteArrayById_postgres" "selectByteArray_postgres", on may 18th… So that issue should be solved in the 5.6 version afaik.</SPAN></BODY></HTML> Thu, 16 Jun 2011 14:01:59 GMT https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71648#M46424 frederikherema1 2011-06-16T14:01:59Z Re: possible bug concerning PostgreSQL https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71649#M46425 <HTML><HEAD></HEAD><BODY><SPAN>sorry, it seems that i messed up my 5.6 check out</SPAN><BR /><BR /><SPAN>kidn regards</SPAN><BR /><SPAN>Philipp Eichhorn</SPAN></BODY></HTML> Thu, 16 Jun 2011 14:35:07 GMT https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71649#M46425 pcsquirrel 2011-06-16T14:35:07Z Re: possible bug concerning PostgreSQL https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71650#M46426 <HTML><HEAD></HEAD><BODY><SPAN>But thanks for reporting anyway! Keep it coming (well, hopefully you encounter no more issues) <img id="smileywink" class="emoticon emoticon-smileywink" src="https://connect.hyland.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /></SPAN></BODY></HTML> Thu, 16 Jun 2011 14:47:50 GMT https://connect.hyland.com/t5/alfresco-archive/possible-bug-concerning-postgresql/m-p/71650#M46426 frederikherema1 2011-06-16T14:47:50Z