Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0038435
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformminorhave not tried2018-04-24 13:152022-02-01 08:08
ReporteraferrazView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0038435: ad_get_preference_value function shows a warning: record "selpref" is not assigned yet

Descriptionad_get_preference_value function shows a warning: record "selpref" is not assigned yet
Steps To ReproduceRun pgpgsql-check and check for ad_get_preference_value warning.
TagsNo tags attached.
Attached Filesdiff file icon 38435.diff [^] (825 bytes) 2018-04-24 13:21 [Show Content]
? file icon 38435.hgexport [^] (6,153 bytes) 2018-04-25 12:45

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0037481 closedshuehner unused PL variables - platform 

-  Notes
(0104053)
aferraz (manager)
2018-04-24 13:20
edited on: 2018-04-24 13:20

Attached fix makes PreferenceTest to fail: https://ci.openbravo.com//job/try-checks-oracle/6773/ [^]

(0104074)
alostale (manager)
2018-04-25 12:48

Attached WiP version.

As it is, it works in ORA but not in PG:

selPref := null;
...
if (selPref.ad_preference_id is null) ...

Changing it to

selPref := null;
...
if (ad_preference_id is null) ...

Works in PG but not in ORA.

In addition beacuse of DBSM translation, selPref ad_preference%ROWTYPE is converted to selPref RECORD, this causes pg_checks to complain about unknown columns in generic record.
(0105177)
alostale (manager)
2018-06-15 11:37

Moved to design defect:
* there's no a simple way to write a code working both in Oracle and PostgreSQL
* this case is already white listed in CI

- Issue History
Date Modified Username Field Change
2018-04-24 13:15 aferraz New Issue
2018-04-24 13:15 aferraz Assigned To => platform
2018-04-24 13:15 aferraz Modules => Core
2018-04-24 13:15 aferraz Triggers an Emergency Pack => No
2018-04-24 13:20 aferraz Note Added: 0104053
2018-04-24 13:20 aferraz Note Edited: 0104053 View Revisions
2018-04-24 13:21 aferraz File Added: 38435.diff
2018-04-24 13:23 aferraz Relationship added related to 0037481
2018-04-24 15:42 alostale Assigned To platform => alostale
2018-04-25 12:45 alostale File Added: 38435.hgexport
2018-04-25 12:48 alostale Note Added: 0104074
2018-04-25 12:48 alostale Assigned To alostale => platform
2018-04-25 12:48 alostale Status new => acknowledged
2018-06-15 11:37 alostale Note Added: 0105177
2018-06-15 11:37 alostale Type defect => design defect
2022-02-01 08:08 alostale Assigned To platform => Triage Platform Base


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker