Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0002987 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] 07. Sales management | minor | always | 2008-05-30 17:46 | 2008-06-18 18:50 | |||
Reporter | user71 | View Status | public | |||||
Assigned To | cromero | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | 2.40alpha-r3 | |||
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 | 0002987: Error: AccessTableNoView in two reports in Sales | |||||||
Description | Description: Sales Dimensional Report and Invoice (customer) Dimensional Report seem to not have permission to be showed independtly if the user has or not permission. It only happens in Postgre Environment: FF2 2.35 MP4 Postgre 8.2 Steps: 1.Log in as Big Bazaar Admin 2.Go to Sales Management > Analysis tools > Sales Dimensional Report. Error: AccessTableNoView message appears. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
![]() |
||||||||
|
![]() |
|
(0003716) cromero (viewer) 2008-06-02 10:03 edited on: 2008-06-12 09:26 |
Logged In: YES user_id=1500614 Originator: NO This problem is due to the different interpretation of a Boolean that drivers do. For Oracle, if the value returned is different of 0, then it is true. For PostgreSQL, if the value returned is different of 1, then it is false. In this case, the problem is that the report has more than 1 permission, so the returned 2 is interpreted as a FALSE in PostgreSQL and TRUE in Oracle. The solution will be to modify the sqlc methos when returning a boolean to return always a boolean and not a number. |
(0003717) cromero (viewer) 2008-06-05 16:38 edited on: 2008-06-12 09:26 |
Logged In: YES user_id=1500614 Originator: NO Fixed in the trunk in revision r4849 |
(0006576) 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=1979432 [^] |
![]() |
|||
Date Modified | Username | Field | Change |
2008-06-18 18:50 | plujan | Status | resolved => closed |
Copyright © 2000 - 2009 MantisBT Group |