Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0017018Openbravo ERPA. Platformpublic2011-05-05 09:492015-02-24 11:13
vmromanos 
marvintm 
normalminorhave not tried
closedduplicate 
20Debian 5.0
 
 
Core
No
0017018: DalStoredProcedureTest.testCallProcess fails only in Oracle
Due to the clean-up project (i.e., removing deprecated/old/unused stuff in Core), I have modified the DalStoredProcedureTest.testCallProcess JUnit test (the table and process used are no longer available in core)

When modifying it, I have tried to keep your original structure, and just change the necessary code (diff attached):
1. I have set core as indevelopment (to override a trigger check)
2. I have modified the original db process by another one that essential does the same: copying some records (fields) from the database

The problem we have seen is that the process fails just in Oracle (http://builds.openbravo.com/job/int-dbcons-oracle/1602/console [^]). As you can see, when exporting the DB, all the fields created by the process are exported, so the database has been modified.
If you take a look at the end of the method, there is a rollback call that shouldn't commit the changes.
What is strange is that this code is working fine in PostgreSQL.


Right now the test is deactivated, so the integration process is not stopped.

FYI: the Oracle instance where it fails has the AUTOCOMMIT = OFF
No tags attached.
duplicate of design defect 0028875 acknowledged Triage Platform Base Class "CallStoredProcedure" does not support parameters of type out 
diff DalStoredProcedureTest-cleanup.diff (5,444) 2011-05-05 09:49
https://issues.openbravo.com/file_download.php?file_id=3941&type=bug
Issue History
2011-05-05 09:49vmromanosNew Issue
2011-05-05 09:49vmromanosAssigned To => mtaal
2011-05-05 09:49vmromanosFile Added: DalStoredProcedureTest-cleanup.diff
2011-05-05 09:49vmromanosModules => Core
2011-05-16 10:06alostaleStatusnew => scheduled
2011-11-04 19:56mtaalAssigned Tomtaal => marvintm
2015-02-24 11:12alostaleRelationship addedrelated to 0028875
2015-02-24 11:12alostaleRelationship replacedhas duplicate 0028875
2015-02-24 11:13alostaleRelationship replacedduplicate of 0028875
2015-02-24 11:13alostaleStatusscheduled => closed
2015-02-24 11:13alostaleResolutionopen => duplicate

There are no notes attached to this issue.