Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002987Openbravo ERP07. Sales managementpublic2008-05-30 17:462008-06-18 18:50
Reporteruser71 
Assigned Tocromero 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version2.40alpha-r3 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0002987: Error: AccessTableNoView in two reports in Sales
DescriptionDescription:
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.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on backport 0003748 closed cromero Error: AccessTableNoView in two reports in Sale 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-06-18 18:50plujanStatusresolved => closed

Notes
(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 [^]
(0003716)
cromero   
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   
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