Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0017630 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
backport | [Openbravo ERP] A. Platform | minor | have not tried | 2009-12-01 13:35 | 2011-07-15 18:23 | |||
Reporter | marvintm | View Status | public | |||||
Assigned To | shuehner | |||||||
Priority | urgent | Resolution | fixed | Fixed in Version | ||||
Status | closed | Fix in branch | 2.50 | Fixed in SCM revision | 56dc0ea11374 | |||
Projection | none | ETA | none | Target Version | 2.50MP32 | |||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Review Assigned To | ||||||||
Web browser | ||||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0017630: Constraint error text parser on Postgres doesn't work with Spanish translated PostgreSQL | |||||||
Description | The constraint error text parser doesn't work on Spanish translated PostgreSQL. For example, this error message is not parsed correctly: ERROR: llave duplicada viola restricción de unicidad «ad_message_value_un» The problem is the different quotes that the Spanish message uses: "<< >>". | |||||||
Steps To Reproduce | Just add a new message entry in the application, in Postgre. The standard constraint error will be shown, instead of the Openbravo customized, "nice" one. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0039086) hgbot (developer) 2011-07-15 11:54 |
Repository: erp/stable/2.50 Changeset: 56dc0ea113749daae8f0c44b54e13373d4b85f20 Author: Stefan Hühner <stefan.huehner <at> openbravo.com> Date: Fri Jul 15 11:53:47 2011 +0200 URL: http://code.openbravo.com/erp/stable/2.50/rev/56dc0ea113749daae8f0c44b54e13373d4b85f20 [^] Fixed 17630 Allow «» also as separators when searching for constraint name Spanish translation of pgsql error messages uses «» instead of "" as quotes around the columnname. Add that case to error text parser for postgres to be able to find the constraint name and show a nicer error message. Also add unit test for this. As language config of db is normally not in spanish that added test just passes in known string into errror text-parser and does not really test db-action vs. expected message like the other testcases. --- M src-test/org/openbravo/test/system/ErrorTextParserTest.java M src/org/openbravo/erpCommon/utility/ErrorTextParserPOSTGRE.java --- |
Issue History | |||
Date Modified | Username | Field | Change |
2011-06-13 18:33 | shuehner | Type | defect => backport |
2011-06-13 18:33 | shuehner | fix_in_branch | => 2.50 |
2011-06-13 18:33 | shuehner | Target Version | 3.0MP2 => 2.50MP32 |
2011-07-15 11:54 | hgbot | Checkin | |
2011-07-15 11:54 | hgbot | Note Added: 0039086 | |
2011-07-15 11:54 | hgbot | Status | scheduled => resolved |
2011-07-15 11:54 | hgbot | Resolution | open => fixed |
2011-07-15 11:54 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/stable/2.50/rev/56dc0ea113749daae8f0c44b54e13373d4b85f20 [^] |
2011-07-15 18:23 | marvintm | Status | resolved => closed |
Copyright © 2000 - 2009 MantisBT Group |