dpQuery got an error when history period have a value NULL

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
Search
Advanced search
Post Reply
1 post • Page 1 of 1
User avatar
vladimir
Posts: 25
Joined: Thu Jan 23, 2014 1:34 pm

dpQuery got an error when history period have a value NULL

Post by vladimir »

Hello!


When history data have a NULL value, the dpQuery with TIMERANGE got an error.

Value NULL happens when driver get some big or little value, PARA shows "-nan(ind)", history table have NULL for this values.
Is there mistake?

3.17 p014, Windows, RDB, Oracle

https://drive.google.com/file/d/1JhFSOo ... sp=sharing
https://drive.google.com/file/d/1_5Phqn ... sp=sharing
Top
Post Reply
1 post • Page 1 of 1

Return to “Bugs / Problems”