BIGINT types lose precision above safe integer limit

[archiewood]

SELECT 9223372036854775807 AS max_bigint;

Expected

max_bigint
---
9223372036854775807

Result

max_bigint
---
9223372036854776000

[JWambaugh]

I am having this issue as well.
Mysql database: 1498392753700442114
In Evidence: 1498392753700442000

For my usecase, I'd be fine if there was a way to get the value as a string instead.

EDIT: I worked around this by converting the bigint value to char in my source sql:

    CONVERT(twitter_id, char) as twitter_id,

[archiewood]

I think you meant to post this at https://github.com/evidence-dev/evidence?

[JWambaugh]

I think you meant to post this at https://github.com/evidence-dev/evidence?

Ah yes, my bad. google took me here. Feel free to delete my comments