<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Activiti SQL for upgrading from 5.2 to 5.3... in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-sql-for-upgrading-from-5-2-to-5-3/m-p/30042#M15401</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Indeed, eg. the file/activiti-engine/src/main/resources/org/activiti/db/upgrade/activiti.oracle.upgradestep.52.to.53.history.sql contains script that is executed when upgrading history from 5.2 to 5.3. This can also contain Java-steps (eg. execute java org.activiti.engine.impl.db.upgrade.DbUpgradeStep52To53InsertPropertyHistoryLevel).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;By combining all scripts (history, engine, …) + java-steps for your DB, you can see what happens in the upgrade. Offcourse, the java-steps may contain additional logic that cannot be translated to SQL, but as long as you can translate it, this is the only way to upgrade manually (although not recommended).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;There is currently no way of doing a "dry run" which just prints out the updates.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Mar 2011 07:07:54 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2011-03-04T07:07:54Z</dc:date>
    <item>
      <title>Activiti SQL for upgrading from 5.2 to 5.3...</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-sql-for-upgrading-from-5-2-to-5-3/m-p/30041#M15400</link>
      <description>Folks-&amp;nbsp; We use liquibase to manage our database, so I need to create a SQL script for updating from 5.2 to 5.3. For this, I'm planning on just doing the following:1) Copy the SQL from activiti.postgres.upgradestep.52.to.53.history.sql2) following SQL updates:update act_ge_property set rev_ = 2, valu</description>
      <pubDate>Thu, 03 Mar 2011 18:38:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-sql-for-upgrading-from-5-2-to-5-3/m-p/30041#M15400</guid>
      <dc:creator>wolpert</dc:creator>
      <dc:date>2011-03-03T18:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti SQL for upgrading from 5.2 to 5.3...</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-sql-for-upgrading-from-5-2-to-5-3/m-p/30042#M15401</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Indeed, eg. the file/activiti-engine/src/main/resources/org/activiti/db/upgrade/activiti.oracle.upgradestep.52.to.53.history.sql contains script that is executed when upgrading history from 5.2 to 5.3. This can also contain Java-steps (eg. execute java org.activiti.engine.impl.db.upgrade.DbUpgradeStep52To53InsertPropertyHistoryLevel).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;By combining all scripts (history, engine, …) + java-steps for your DB, you can see what happens in the upgrade. Offcourse, the java-steps may contain additional logic that cannot be translated to SQL, but as long as you can translate it, this is the only way to upgrade manually (although not recommended).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;There is currently no way of doing a "dry run" which just prints out the updates.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 07:07:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-sql-for-upgrading-from-5-2-to-5-3/m-p/30042#M15401</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2011-03-04T07:07:54Z</dc:date>
    </item>
  </channel>
</rss>

