0016208: Dal-Identifier calculation is using wrong order among the identifier fields defined for the table.

Description

If a table contains more than one field marked as identifier then the order among those fields is defined via the column ad_column.seqno (see i.e. ComboTableQuery_data.xsql or src-db/database/model/functions/AD_COLUMN_IDENTIFIER_SQL.xml).

DAL identifier calculation doesn't use this but instead reuses ad_column.position which is the standard order of the columns inside the table.

Example:
dal-identifier:
address spain - - Pamplona - 31002 - United States -
sql-identifier:
address spain - - 31002 - Pamplona - - United States

Which have different column ordering.

Steps To Reproduce

See attached diff for a junit testcase which exposes the issue for the table c_location, as it has identifier columns defined with an ordering different from the column order in the table.

Proposed Solution

When populating list of identifierColumns in org.openbravo.base.model.Table reorder the list by seq (which needs to be added to the mapping & file first).

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

duplicate of

defect

0018698

closed

alostale

Grid identifiers don't take seqno into account

Notes
(0034734) shuehner (administrator) 2011-03-10 16:21	Note: problem most likely exists in 2.50 as well.

Issue History
Date Modified	Username	Field	Change
2011-03-10 16:21	shuehner	New Issue
2011-03-10 16:21	shuehner	Assigned To	=> shuehner
2011-03-10 16:21	shuehner	Modules	=> Core
2011-03-10 16:21	shuehner	OBNetwork customer	=> No
2011-03-10 16:21	shuehner	Note Added: 0034734
2011-03-14 10:56	alostale	Status	new => scheduled
2011-10-05 12:51	alostale	Relationship added	duplicate of 0018698
2011-10-05 12:51	alostale	Status	scheduled => closed
2011-10-05 12:51	alostale	Resolution	open => duplicate