0
Answered

Query T001F065_ACTUAL_POSITION_NO in IdB 5.x Aurion Position query

Matthew Woolnough 2 years ago in UNIFYBroker/Aurion • updated by anonymous 2 years ago 5

Client DBA was able to determine that the Aurion position connector actually runs 3 queries in IDB version 3 and 5.  

The first and third are identical but the second script is totally different. 

In version 3, the position appears to be retrieved from "T001F065_ACTUAL_POSITION_NO" whereas in version 5 appears to try to determine position information from "T101F005_POSITION_NO". 

Is it possible to have the position query retrieve data from "T001F065_ACTUAL_POSITION_NO" in IdB 5.x?



Affected Versions:
Fixed by Version:

Answer

Answer

OK, It sounds as though there is a misalignment between dev & prod. Will ask them to update the environment.

GOOD, I'M SATISFIED
Satisfaction mark by Matthew Woolnough 2 years ago
Under review

What query are you referring to? If it's the Aurion query - it's completely up to you what comes back. Just change the query in the query editor.

So it's independent of the connector? They can make any changes they like to this query?


https://unifysolutions.jira.com/wiki/display/IDBAUR51/Specifications

So it's independent of the connector?

Yes, the connector points to whatever query you like. That's why there is the schema mapping - so that the query fields are mapped to the connector fields.

They can make any changes they like to this query?

Correct - in the Aurion query tool.

Answer

OK, It sounds as though there is a misalignment between dev & prod. Will ask them to update the environment.