0009287: Errors thrown from triggers with code -20000 are not correctly displayed in Oracle

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0009287

Openbravo ERP

A. Platform

public

2009-06-02 12:13

2009-07-27 00:00

Reporter

AinhoaPagola

Assigned To

shuehner

Priority

urgent

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Ubuntu 8.4

Product Version

main

Target Version

Fixed in Version

2.50MP3

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

Summary

0009287: Errors thrown from triggers with code -20000 are not correctly displayed in Oracle

Description

If an error message with code -20000 is thrown from a trigger in Oracle, the error message displayed in the application contains the error message and some extra unnecessary information.

Example:

There is already one default setup record. Only one record is allowed.
ORA-06512: en "MAINHCM.HCMC_DEFAULT_TRG", línea 35
ORA-04088: error durante la ejecución del disparador 'MAINHCM.HCMC_DEFAULT_TRG'

Notice that the first sentence is the msgtext of the error message thrown.
This only happens if the error code used is -20000, it works fine with other codes.

This problem is not visible in core because every single error thrown in a trigger has a numeric code in its message value. In modules, the value of the message must start with the prefix so it is not posible to set a number to it an skip this problem.

This problem is not reproducible in functions. The translation is properly done in that case. It is also not reproduceable in PostgreSQL, it works fine for triggers and functions.

That is, this problem happens: In oracle, for message with string value thrown in triggers.

Steps To Reproduce

- Create a message in add_message with a string value. That is, do not use a numeric value (like 20540) but a string (example "MoreThanOneRecord").
- Raise the error from a trigger. Use this instruction:
RAISE_APPLICATION_ERROR(-20000,'@HCMC_OneDefaultRecord@');
- In the application, perform the action that launches the trigger. The error displayed in the error box contains the error message properly translated and some extra error message that shouldn't be visible.

Proposed Solution

Additional Information