You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Converting the value to a char in the source lets me get the full-precision value as a string, which works for my use case, but it could be problematic if I was trying to put it into a graph.
The text was updated successfully, but these errors were encountered:
Describe the bug
When reading a bigint value from my mysql database, bigint values are losing their precision inside of evidence.
For example:
Mysql database: 1498392753700442114
In Evidence: 1498392753700442000
In my use case, string values are sufficient, so I was able to work around this issue by converting it to a
char
in my source query:Steps to Reproduce
1498392753700442114
1498392753700442000
Logs
System Info
Severity
serious, but I can work around it
Additional Information, or Workarounds
Converting the value to a
char
in the source lets me get the full-precision value as a string, which works for my use case, but it could be problematic if I was trying to put it into a graph.The text was updated successfully, but these errors were encountered: