Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0002486 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] 09. Financial management | minor | always | 2008-01-09 10:18 | 2008-07-04 19:05 | |||
Reporter | user71 | View Status | public | |||||
Assigned To | cromero | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | 2.40beta | |||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | ||||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Merge Request Status | ||||||||
Review Assigned To | ||||||||
OBNetwork customer | No | |||||||
Web browser | ||||||||
Modules | Core | |||||||
Support ticket | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0002486: Saving records in Payment Status Management Lines | |||||||
Description | Merely clicking the 'Save' button in : Financial Management->Receivables & Payables->Transactions->Payment Status Management->Header->Lines will produce error : "ERROR : COALESCE types character and integer cannot be matched' I found the offending codes in database trigger "c_dpmline_chk_restriction_trg" line 15: ... OR(COALESCE(OLD.STATUS_FROM, 0) <> COALESCE(NEW.STATUS_FROM, 0)) OR(COALESCE(OLD.STATUS_TO, 0) <> COALESCE(NEW.STATUS_TO, 0)))) THEN Changing it to ... OR(COALESCE(OLD.STATUS_FROM, '') <> COALESCE(NEW.STATUS_FROM, '')) OR(COALESCE(OLD.STATUS_TO, '') <> COALESCE(NEW.STATUS_TO, '')))) THEN Seems to solve the problem. Is this correct?, please advice. Openbravo 2.35 Debian Etch Postgresql 8.2/lenny Tomcat5.5 Java 1.5 | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
![]() |
||||||||
|
![]() |
|
(0002981) cromero (viewer) 2008-01-29 12:50 edited on: 2008-06-12 09:24 |
Logged In: YES user_id=1500614 Originator: NO Fixed in the trunk since revision 2166. Yes you are right, in PostgreSQL is not allowed to use different types of data in a COALESCE (Oracle makes cast automatically). Carlos Romero Openbravo Team |
(0006075) user71 2005-06-01 00:00 edited on: 2008-06-12 09:43 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1867543 [^] |
![]() |
|||
Date Modified | Username | Field | Change |
2008-07-04 19:05 | plujan | Status | resolved => closed |
2008-07-04 19:05 | plujan | Fixed in Version | 2.40alpha-r2 => 2.40beta |
Copyright © 2000 - 2009 MantisBT Group |