0004681: Prepaid sales orders crashes when completing in postgres

Notes
(0008890) cromero (reporter) 2008-09-05 11:45	The problem in PostgreSQL is that we are trying to catch a code exception 'DATA_EXCEPTION' when we should use 'RAISE_EXCEPTION' ''RAISE EXCEPTION presently always generates the same SQLSTATE code, P0001, no matter what message it is invoked with. It is possible to trap this exception with EXCEPTION ... WHEN RAISE_EXCEPTION THEN ... but there is no way to tell one RAISE from another.'' So, now we are using exceptions like NO_DATA_FOUND (Oracle) that it is translated to DATA_EXCEPTION (PostgreSQL), but it does not work since we are trying to catch an exception code that is never thrown. What we should do in Postgres would be something like: RAISE EXCEPTION '%', 'ORACLE_EXCEPTION_CODE'; EXCEPTION WHEN RAISE_EXCEPTION THEN --OBTG:ORACLE_EXCEPTION_CODE --

(0010156) rafaroda (developer) 2008-11-11 11:59	This bug still reproduces in the trunk. It seems to be an odd behavior in the messaging of C_OrderPOST1 procedure [1]. See lines 175-177 (in the XML file): IF (v_DocSubTypeSO='PR' AND v_invoicerule <> 'I') THEN RAISE_APPLICATION_ERROR(-20000, '@PrepayMustImmediate@'); END IF; [1] https://dev.openbravo.com/websvn/openbravo/trunk/src-db/database/model/functions/C_ORDER_POST1.xml [^]