|
|
博学的紫菜汤 · 修改和美化安卓系统的第一步~从认识APK开始 ...· 2 年前 · |
|
|
坏坏的西瓜 · 张若昀:中学有变态情结 想和李易峰下棋_手机新浪网· 2 年前 · |
|
|
高大的山羊 · stitch是什么意思,stitch怎么读, ...· 3 年前 · |
|
|
好帅的土豆 · 苍穹的法芙娜_抖抖音· 3 年前 · |
|
|
微醺的大象 · 基于nodejs如何实现http传输大文件? ...· 3 年前 · |
I'm currently working on a new feature for Hypothesis, where we can dump a tidy jsonlines table of all the test cases we tried - including arguments, outcomes, timings, coverage, etc. Exploring this seems like a perfect cases for
sqlite-utilsanddatasette, but I pretty quickly ran into an integer overflow problem and don't want to recommend that experience to my users.I originally went to report this as a bug... and then found #309 (comment) almost exactly matched my repro 😅
#110 (comment) suggests that using
NUMERICwould avoid this overflow error, although "If the TEXT value is a well-formed integer literal that is too large to fit in a 64-bit signed integer, it is converted to REAL." suggests that this would come at the cost of rounding to the nearest float value. Maybe I should just convert large integers to float before writing out my json?After a bit more hacking, "manually cast large integers to float" seems like a decent solution for my particular case, but having written it up I thought I might as well post this issue anyway - I hope it's useful feedback, and won't mind at all if you close as wontfix if it's not.