Skip to content

Frontier access hardcode DB type for 3 columns in the run 2 TriggerDB

Joerg Stelzer requested to merge stelzer/athena:24.0-frontierTypeResolution into 24.0

This is needed because frontier does not report the scale value Y for DB-type NUMBER(X,Y) and we can not distinguish between int (Y=0) and float (Y>0) when turning the returned query string into actual numbers.

In the Run 2 TriggerDB there are only 3 fields that are of type NUMBER(X,Y) with Y>0 and there are none in the Run 1 TriggerDB.

This addresses ATR-29885

Edited by Joerg Stelzer

Merge request reports