Related to issue 20350: do not use status column in ad_alert.
authorMikel Irurita <mikel.irurita@openbravo.com>
Wed, 16 May 2012 18:03:53 +0200
changeset 16564 5e580de24a96
parent 16563 90cdb77c016b
child 16565 a683fa9bce54
Related to issue 20350: do not use status column in ad_alert.
Status column in ad_alert table does not exist on 2.50.
src-util/buildvalidation/build/classes/org/openbravo/buildvalidation/AccountingTabsData.class
src-util/buildvalidation/src/org/openbravo/buildvalidation/AccountingTabs_data.xsql
Binary file src-util/buildvalidation/build/classes/org/openbravo/buildvalidation/AccountingTabsData.class has changed
--- a/src-util/buildvalidation/src/org/openbravo/buildvalidation/AccountingTabs_data.xsql	Wed May 16 18:07:34 2012 +0200
+++ b/src-util/buildvalidation/src/org/openbravo/buildvalidation/AccountingTabs_data.xsql	Wed May 16 18:03:53 2012 +0200
@@ -130,9 +130,8 @@
    	<Sql>
    		<![CDATA[
        INSERT INTO AD_Alert (AD_Alert_ID, AD_Client_ID, AD_Org_ID, IsActive, 
-                      Created, CreatedBy, Updated, UpdatedBy, Description, AD_AlertRule_ID, Record_Id, Referencekey_ID,
-                      status)
-      		VALUES (get_uuid(), '0', '0', 'Y', NOW(), '0', NOW(), '0', ?, ?, ?, ?, 'NEW')
+                      Created, CreatedBy, Updated, UpdatedBy, Description, AD_AlertRule_ID, Record_Id, Referencekey_ID)
+      		VALUES (get_uuid(), '0', '0', 'Y', NOW(), '0', NOW(), '0', ?, ?, ?, ?)
       ]]>
    	</Sql>
    	<Parameter name="description" />