Openbravo Issue Tracking System - Openbravo ERP | |||||||||||||||||||
View Issue Details | |||||||||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||||||||
0004859 | Openbravo ERP | 03. Procurement management | public | 2008-09-08 17:36 | 2008-12-03 13:56 | ||||||||||||||
Reporter | rafaroda | ||||||||||||||||||
Assigned To | cromero | ||||||||||||||||||
Priority | high | Severity | minor | Reproducibility | always | ||||||||||||||
Status | closed | Resolution | fixed | ||||||||||||||||
Platform | OS | 20 | OS Version | Ubuntu 7.10 | |||||||||||||||
Product Version | pi | ||||||||||||||||||
Target Version | Fixed in Version | ||||||||||||||||||
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 | No | ||||||||||||||||||
Summary | 0004859: 'Purchase Order Report' does not work in PostgreSQL | ||||||||||||||||||
Description | 'Purchase Order Report' does not work in PostgreSQL if you select any of the filters that points to an ID. In Oracle it works. Take into account that this filter window is WAD generated. This is a regression since in Openbravo ERP 2.40 production it worked both in PostgreSQL and Oracle. | ||||||||||||||||||
Steps To Reproduce | 1) Go to 'Procurement Management || Analysis Tools || Purchase Order Report', do not select any filter and click on 'OK' button. Report works correctly. 2) Launch the same report selecting any of the filters that points to an ID (e.g., Business Partner or Project). Report breaks with error: ERROR org.openbravo.erpCommon.utility.PrintJR - Error captured: javax.servlet.ServletException: Error executing SQL statement for : ReportPurchaseOrder Take into account that this filter window is WAD generated. | ||||||||||||||||||
Proposed Solution | The problem is in the dates, that it is always using them in the query even when you don't specify anything. As easy workaround you can set always the dates with any value and it will work fine. | ||||||||||||||||||
Additional Information | |||||||||||||||||||
Tags | No tags attached. | ||||||||||||||||||
Relationships |
| ||||||||||||||||||
Attached Files | |||||||||||||||||||
Issue History | |||||||||||||||||||
Date Modified | Username | Field | Change | ||||||||||||||||
2008-09-08 17:36 | rafaroda | New Issue | |||||||||||||||||
2008-09-08 17:36 | rafaroda | Assigned To | => cromero | ||||||||||||||||
2008-09-08 17:36 | rafaroda | sf_bug_id | 0 => 2100474 | ||||||||||||||||
2008-09-08 17:36 | rafaroda | Regression testing | => No | ||||||||||||||||
2008-09-16 13:09 | cromero | Note Added: 0009034 | |||||||||||||||||
2008-09-16 13:53 | cromero | Status | new => scheduled | ||||||||||||||||
2008-09-16 13:53 | cromero | fix_in_branch | => trunk | ||||||||||||||||
2008-09-16 13:55 | cromero | Severity | major => minor | ||||||||||||||||
2008-09-16 13:55 | cromero | fix_in_branch | trunk => | ||||||||||||||||
2008-09-16 13:55 | cromero | Steps to Reproduce Updated | |||||||||||||||||
2008-09-16 13:56 | svnbot | Checkin | |||||||||||||||||
2008-09-16 13:56 | svnbot | Note Added: 0009035 | |||||||||||||||||
2008-09-16 13:56 | svnbot | Status | scheduled => resolved | ||||||||||||||||
2008-09-16 13:56 | svnbot | Resolution | open => fixed | ||||||||||||||||
2008-09-16 13:56 | svnbot | svn_revision | => 7352 | ||||||||||||||||
2008-10-03 16:03 | rafaroda | Relationship added | related to 0005408 | ||||||||||||||||
2008-12-03 13:56 | krishna | Status | resolved => closed |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|