0012003: Improve handling of default values in the DAL: use the default values which use context information

Description

The DAL currently does not make use of the default values which use context information from VariablesSecureApp or sql queries. There are however possibilities to implement this:

First the DAL needs access to the window_id and variablesecureapp:
- the OBContext is put in a threadlocal when the request starts
… the variablessecureapp and window_id can also be placed in a threadlocal there (depends if the window_id is session var or a request param, in the last case it can not always be just taken from the request, considering multi-part and file upload requests)
- the BaseOBObject constructor should be extended to set the default values using the variablessecureapp/window id in the
- then when a new BaseOBObject is created this constructor sets the default values.

The logic needs to take into account the default values definition with SQL= also.

Note the above logic does not work correctly for test cases as there is variablesecureapp in that environment.

gr. Martin

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2010-01-19 11:30	mtaal	New Issue
2010-01-19 11:30	mtaal	Assigned To	=> mtaal
2010-01-19 11:30	mtaal	OBNetwork customer	=> No
2010-01-19 11:32	mtaal	Status	new => scheduled
2016-10-21 11:05	mtaal	Status	scheduled => closed
2016-10-21 11:05	mtaal	Resolution	open => out of date
2016-10-21 13:17	mtaal	Tag Attached: MT_closed_out_of_date
2016-10-21 14:08	mtaal	Assigned To	mtaal => platform
2016-10-21 14:09	mtaal	Status	closed => new
2016-10-21 14:14	mtaal	Tag Detached: MT_closed_out_of_date
2022-02-01 08:09	alostale	Assigned To	platform => Triage Platform Base