Table operation parameter position inconsistency

[Guillaume]

Hello,

I found on a data model that table FK constraints (operations) have columns with the same position i.e. parameters in t_operationparams for the same operation are defined as follows:
id2 : pos = 0
id1 : pos = 0
othercol : pos = 1

I have a script that controls the order between a PK and FK constraint. Looping on each operation parameters collection, it randomly picks the first column as both have the same position.
Is there a way to fix this inconsistency ?

[qwerty]

Well, no. There is some black magic (probably no fairy dust) in the sort order for attributes/operations. Only if you manually move one they get a reasonable pos set. Else it's a mix of their ID, name and who knows what. I gave up figuring out a rule.

q.