Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0010072
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] Y. DBSourceManagerminorhave not tried2009-07-27 16:092012-03-08 13:07
ReporterAinhoaPagolaView Statuspublic 
Assigned Tomarvintm 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Versionpi
OSLinux 32 bitDatabasePostgreSQLJava version1.5
OS VersionUbuntu 8.4Database version8.3Ant version1.7
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0010072: Code with no indentation is not properly traslated from PostgreSQl to Oracle

DescriptionIf no indentation is inserted in a code line, this is not properly translated.

This is reproducible with RAISE and with PERFORM statements.
Steps To ReproduceExample, 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- 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


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker