Hi all, For a long time, there has been an issue related to the export.database task, which caused unexpected changes in PL/SQL functions and triggers when they are exported from the PostgreSQL database. The main cause for this issue is that the translation process which dbsourcemanager uses requires a very strict syntax to work correctly. This means that if you don't follow exactly the same syntax, format and patterns that the functions and triggers in Core, your own functions and triggers could be exported differently from how they were defined originally in the database.
There has been a change to export.database related to this, which will be included in Openbravo ERP 2.50 MP15, and which right now has already been applied in current pi branch. Export.database now checks if the functions and triggers you are exporting would be imported in a PostgreSQL database with the same definition used to create them in the database. If they are found to be different, a warning is shown, and the differences in both functions are also shown. The developer should then check if the function was changed in a relevant way, or if he can ignore the changes. This change is not relevant for people who work in an Oracle only environment (it is relevant for people who work with Oracle but want their PL/SQL code to work in PostgreSQL also, though). The downside of this check is that it makes export.database a little bit slower, so if you want to disable the check, you can call export.database with the following command: ant export.database -DcheckTranslationConsistency=false Export.database will be quicker, but function and trigger translation will not be checked. We hope that with this change, the development experience with Openbravo ERP will be improved, particularly in situations in which a lot of PL/SQL code is generated. Regards, Antonio. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
