Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0004601Openbravo ERPA. Platformpublic2008-08-08 21:092009-08-18 21:12
rafaroda 
shuehner 
normalminoralways
closedno change required 
20Ubuntu 7.10
pi 
 
Core
No
0004601: Provide way for translated db-error messages without need for hundres mostly-identical translation entries
To get translated database-error messages for i.e. a database 'not null' constraint, we currently need an new individual AD_MESSAGE entry per individual constraint.

A way to have one generic message (but filled at runtime with the relevant fieldnane, tablename) would give lots of benefit:

- Less work for translators
- Easier maintenance
- will catch most cases, and still leaves possibility for individual errors for special cases.
1) Logged as System Administrator, make a mandatory column to be not mandatory within Application Dictionary and compile the corresponding window.
2) Logged as a normal user, try to make an insertion or an update to this window and field.

The message attached, that is in the language of the database (that may be the same as user's language or not), is displayed.

Problem is that the individual AD_MESSAGE entry is not present for this message so the original not-localized database message is displayed.
No tags attached.
related to defect 0005625 closed shuehner Improve messaging where there is no conversion rate 
related to defect 00097812.50MP4 closed vmromanos There are some incorrect translations in Spanish translation (I) 
png error-good-format-wad.png (4,908) 2008-08-08 21:09
https://issues.openbravo.com/file_download.php?file_id=203&type=bug
png
Issue History
2008-08-08 21:09rafarodaNew Issue
2008-08-08 21:09rafarodaAssigned To => cromero
2008-08-08 21:09rafarodasf_bug_id0 => 2043458
2008-08-08 21:09rafarodaFile Added: error-good-format-wad.png
2008-08-14 10:26psarobeStatusnew => scheduled
2008-08-14 10:26psarobeAssigned Tocromero => alostale
2008-08-14 10:26psarobefix_in_branch => trunk
2008-12-10 09:58alostaleAssigned Toalostale => iperdomo
2009-02-03 17:53iperdomoAssigned Toiperdomo => shuehner
2009-02-18 18:25shuehnerRelationship addedrelated to 0005625
2009-02-24 19:45shuehnerNote Added: 0014038
2009-02-24 19:45shuehnerStatusscheduled => feedback
2009-02-25 11:16shuehnerStatusfeedback => new
2009-02-25 11:16shuehnerCategoryE. Translation => A. Platform
2009-02-25 11:16shuehnerTypedefect => feature request
2009-02-25 11:16shuehnerfix_in_branchtrunk =>
2009-02-25 11:16shuehnerSummaryDatabase error messages parsed are not translated => Provide way for translated db-error messages without need for hundres mostly-identical translation entries
2009-02-25 11:16shuehnerDescription Updated
2009-02-25 11:16shuehnerProposed Solution updated
2009-02-25 11:16shuehnerSteps to Reproduce Updated
2009-02-25 11:17shuehnerNote Deleted: 0014038
2009-02-25 11:17shuehnerIssue Monitored: shuehner
2009-02-25 11:17shuehnerRelationship addedrelated to 0007236
2009-07-10 14:59pjuvaraRelationship addedrelated to 0009781
2009-07-10 15:00pjuvaraStatusnew => scheduled
2009-07-10 15:00pjuvarafix_in_branch => pi
2009-07-10 15:01pjuvaraNote Added: 0018109
2009-07-10 15:01pjuvarafix_in_branchpi =>
2009-07-10 15:01pjuvaraRelationship deletedrelated to 0007236
2009-08-18 21:12shuehnerStatusscheduled => closed
2009-08-18 21:12shuehnerNote Added: 0019021
2009-08-18 21:12shuehnerResolutionopen => no change required
2009-08-18 21:12shuehnerIssue End Monitor: shuehner

Notes
(0018109)
pjuvara   
2009-07-10 15:01   
Target 2.50 MP5
(0019021)
shuehner   
2009-08-18 21:12   
The needed changes have been implemented as part of fixing defect 9781. Now common auto-generated error messages are used for most common cases.

For the cases not handled, or if a more specific error message is wanted it is still possible to create an ad_message entry per constraint (like before).