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
2016/01/05 11:42:24 Starting Pome 0.1.0
2016/01/05 11:42:24 Application will be available at http://127.0.0.1:2345
2016/01/05 11:42:24 sql: Scan error on column index 3: converting string "1.1198464e+07" to a int: strconv.ParseInt: parsing "1.1198464e+07": invalid syntax
It seems like the problem come from SUM used for the database size. SUM of bigint return a numeric type. I don't think that we will support db above int64 size
I now cat the result to bigint so it should solve the problem.
I wasn't not able to reproduce the bug even when replacing query with SELECT 1.1198464e+07 , 1.1198464e+07::numeric so it will be amazing if you could test b051abf
2016/01/06 10:13:54 Starting Pome 0.1.1
2016/01/06 10:13:54 Application will be available at http://127.0.0.1:2345
2016/01/06 10:13:54 sql: Scan error on column index 3: converting string "1.1198464e+07" to a int: strconv.ParseInt: parsing "1.1198464e+07": invalid syntax
I will publish a verbose mode later tonight, I realize that I added the cast on the wrong db query.
Base on the index 3 then it means that the problem appear on TableBloat.
Thanks for trying and your patience, I'll try get that fixed asap.
2016/01/06 13:52:21 Starting Pome 0.1.1
2016/01/06 13:52:21 Application will be available at http://127.0.0.1:2345
2016/01/06 13:52:21 sql: Scan error on column index 3: converting string "2.031616e+06" to a int: strconv.ParseInt: parsing "2.031616e+06": invalid syntax
I'm getting similar, with 2016/01/07 03:19:55 sql: Scan error on column index 3: converting string "4.145152e+06" to a int: strconv.ParseInt: parsing "4.145152e+06": invalid syntax
Activity
ober commentedon Jan 5, 2016
Hit by it too.
rach commentedon Jan 6, 2016
I will try to get that fixed asap. I suspect that some of the sql query needs some adjustment as the Go Sql lib cannot handle the conversion.
rach commentedon Jan 6, 2016
It seems like the problem come from SUM used for the database size. SUM of bigint return a numeric type. I don't think that we will support db above int64 size
I now cat the result to bigint so it should solve the problem.
I wasn't not able to reproduce the bug even when replacing query with
SELECT 1.1198464e+07 , 1.1198464e+07::numericso it will be amazing if you could test b051abfthanks
honza commentedon Jan 6, 2016
Unfortunately, the problem persists:
The database is pretty small, like 300MB.
I'm using Postgresql 9.4.5 on OSX.
rach commentedon Jan 6, 2016
I will publish a verbose mode later tonight, I realize that I added the cast on the wrong db query.
Base on the
index 3then it means that the problem appear on TableBloat.Thanks for trying and your patience, I'll try get that fixed asap.
internetuser2008 commentedon Jan 6, 2016
Getting same error on Mac OSX Postgres 9.4.4
2016/01/06 13:52:21 Starting Pome 0.1.1
2016/01/06 13:52:21 Application will be available at http://127.0.0.1:2345
2016/01/06 13:52:21 sql: Scan error on column index 3: converting string "2.031616e+06" to a int: strconv.ParseInt: parsing "2.031616e+06": invalid syntax
jmealo commentedon Jan 6, 2016
Same issue using the latest Go and Pome on Ubuntu 14.04 (64-bit).
ThisIsMissEm commentedon Jan 7, 2016
I'm getting similar, with
2016/01/07 03:19:55 sql: Scan error on column index 3: converting string "4.145152e+06" to a int: strconv.ParseInt: parsing "4.145152e+06": invalid syntaxFix #23 Fix #22 Avoid to floating point numbers & scientific notation…
Fix #22 Avoid to floating point numbers & scientific notation with nu…
honza commentedon Jan 7, 2016
The fix works for me, thanks. ✨
rach commentedon Jan 8, 2016
Great. Thanks for testing it. I should have been more careful about the types of some of the SQL query.