Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002551Openbravo ERP01. General setuppublic2008-01-25 09:152008-07-08 11:03
Reporteralostale 
Assigned Toalostale 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version2.40beta 
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
Summary0002551: Alert Rule definition in PG needs fields in capitals
DescriptionEnv.:
Trunk
PostgreSQL

Description:
When an alert rule is defined in PG it expects to have all fields in capital letters (which is the default for Oracle), so the message saying there are fields not included appears though they actually are.

Workarround:
In the query set aliases in capital letters within double quotas ("). Example:

select ad_client_id as "AD_CLIENT_ID"
       ad_role as "AD_ROLE_ID"
...
from ...
...
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on backport 0003621 closed alostale AlertRule definition in PG needs capital letters 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-07-08 11:03psarobeStatusresolved => closed
2008-07-08 11:03psarobeFixed in Version2.40alpha-r2 => 2.40beta

Notes
(0006140)
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=1879482 [^]
(0003089)
alostale   
2008-01-28 10:30   
(edited on: 2008-06-12 09:24)
Logged In: YES
user_id=1500722
Originator: YES

Tip:
*SL_AlerRule_SQL.existsColumn is checking the name taking into account the case. It shouldn't.
*Check the way background process is looking for the column name.