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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0007618
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 00. Application dictionaryminorhave not tried2009-02-18 10:232009-04-22 00:00
ReporterDowidView Statuspublic 
Assigned Toshuehner 
PriorityhighResolutionfixedFixed in Version2.50beta
StatusclosedFix in branchpiFixed in SCM revision13482
ProjectionnoneETAnoneTarget Version
OSWindowsDatabasePostgreSQLJava version1.6
OS VersionSP2Database 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

0007618: AD_MESSAGE with the search key that matches constraint name doesn't work in Postgres

DescriptionApplication Dictionary->Message
 
When creating an error message that is related to a contraint in the database, the OBError displays this message in Oracle but does not display the message in Postgres.
Steps To Reproduce1. Go to Application Dictionary->Message
2. Search meassage with Search key "AD_USER_UN_USERNAME". Message related to thise constraint "Already exists a user with the same User name . Input a different one"

3. Test this message in Oracle and Postgres. Please follow steps in [1]

Note that this message is displayed correctly in Oracle, and incorrectly in Postgres. Furthermore, this behavior is true for all errors that are related to contraints in the Postgres, but works in Oracle.
 

[1] https://issues.openbravo.com/view.php?id=6989 [^]
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
depends on backport 0007729 closedshuehner AD_MESSAGE with the search key that matches constraint name doesn't work in Postgres 
related to defect 0005625 closedshuehner Improve messaging where there is no conversion rate 
blocks defect 0006989pi closedDowid Duplicate user error message should be displayed in correct context 
blocks feature request 0002695 closedDowid Message when creating duplicate File Formats is not clear 

-  Notes
(0013632)
rafaroda (developer)
2009-02-18 11:32

Hi David,

I do not agree with what you say.
1) Go to 'Project & Service Management || Transactions || Expense Sheet' and create a new expense.
2) Go to Lines tab and tick Reinvoicing check WITHOUT selecting a business partner.
3) Save.
      
Error message displays: "You have checked Reinvoicing. You must also select the corresponding Business Partner."

This message is displaying correctly in PostgreSQL and is defined in AD_MESSAGE through a constraint name: "S_TIMEEXPENSELINE_CHECK1"

select * from ad_message where msgtext like '%You have checked Reinvoicing%';
(0013646)
Dowid (reporter)
2009-02-18 13:19
edited on: 2009-02-18 13:32

Rafa,

What I meant was constraints that have unique type. Your example is related to the check type constraint. For contraints with the check type it works, but for unique constraint type we get incorrect behavior in Postgres.

By executing this select you will be able to see these constraints:

Select pgc.conname, m.msgtext from pg_constraint pgc , AD_Message m
where pgc.contype ='u'
and Upper(m."value") like Upper(pgc.conname)

(0013689)
rafaroda (developer)
2009-02-18 18:21

Thank you for the clarification David.
(0013700)
shuehner (administrator)
2009-02-18 20:22

This problem does happen for the following constraint types:

- unique, and primary key (unique implicitely)

The following constraint types are ok:

- check constraint
- foreign key
- not null
(0013860)
svnbot (reporter)
2009-02-20 17:33

Repository: openbravo
Revision: 13482
Author: huehner
Date: 2009-02-20 17:32:58 +0100 (Fri, 20 Feb 2009)

Fixed 7618
Fix parsing of postgres error messages so that ad_message entries for a specific
constraint violation are correctly found

---
U trunk/src/org/openbravo/erpCommon/utility/ErrorTextParserPOSTGRE.java
---

https://dev.openbravo.com/websvn/openbravo/?rev=13482&sc=1 [^]

- Issue History
Date Modified Username Field Change
2009-02-18 10:23 Dowid New Issue
2009-02-18 10:23 Dowid Assigned To => rafaroda
2009-02-18 10:23 Dowid Regression testing => No
2009-02-18 10:24 Dowid Relationship added blocks 0006989
2009-02-18 10:25 Dowid Relationship added blocks 0002695
2009-02-18 11:32 rafaroda Note Added: 0013632
2009-02-18 11:32 rafaroda Status new => feedback
2009-02-18 13:19 Dowid Note Added: 0013646
2009-02-18 13:32 Dowid Note Edited: 0013646
2009-02-18 18:21 rafaroda Note Added: 0013689
2009-02-18 18:21 rafaroda Assigned To rafaroda => shuehner
2009-02-18 18:21 rafaroda Priority normal => high
2009-02-18 18:21 rafaroda Status feedback => scheduled
2009-02-18 18:25 shuehner Relationship added related to 0005625
2009-02-18 20:22 shuehner Note Added: 0013700
2009-02-20 17:29 shuehner Status scheduled => acknowledged
2009-02-20 17:29 shuehner Status acknowledged => scheduled
2009-02-20 17:29 shuehner fix_in_branch => trunk
2009-02-20 17:33 svnbot Checkin
2009-02-20 17:33 svnbot Note Added: 0013860
2009-02-20 17:33 svnbot Status scheduled => resolved
2009-02-20 17:33 svnbot Resolution open => fixed
2009-02-20 17:33 svnbot svn_revision => 13482
2009-04-21 10:33 psarobe Status resolved => closed
2009-04-22 00:00 anonymous sf_bug_id 0 => 2777923


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker