Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0010072 | Openbravo ERP | Y. DBSourceManager | public | 2009-07-27 16:09 | 2012-03-08 13:07 |
Reporter | AinhoaPagola | ||||
Assigned To | marvintm | ||||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | scheduled | Resolution | open | ||
Platform | OS | 20 | OS Version | Ubuntu 8.4 | |
Product Version | pi | ||||
Target Version | pi | Fixed in Version | |||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Web browser | |||||
Modules | Core | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0010072: Code with no indentation is not properly traslated from PostgreSQl to Oracle | ||||
Description | If no indentation is inserted in a code line, this is not properly translated. This is reproducible with RAISE and with PERFORM statements. | ||||
Steps To Reproduce | Example, on a postgresql function, add the following line WITH NO INDENTATION PERFORM C_ORDER_POST1(NULL, v_Order_ID); It will be translated in the xml file as: PERFORM C_ORDER_POST1(NULL, v_Order_ID); If you indent it, it will be translated as C_ORDER_POST1(NULL, v_Order_ID); as it should be. This also happens with RAISE NOTICE statement. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2009-07-27 16:09 | AinhoaPagola | New Issue | |||
2009-07-27 16:09 | AinhoaPagola | Assigned To | => marvintm | ||
2009-08-17 13:24 | rafaroda | Status | new => scheduled | ||
2009-08-17 13:24 | rafaroda | version | => pi | ||
2012-03-08 13:07 | marvintm | Type | defect => design defect |
There are no notes attached to this issue. |