Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scan error #23

Closed
kkoch986 opened this issue Jan 5, 2016 · 7 comments
Closed

Scan error #23

kkoch986 opened this issue Jan 5, 2016 · 7 comments

Comments

@kkoch986
Copy link

kkoch986 commented Jan 5, 2016

Tried starting it up and got the following error:

2016/01/05 10:33:02 Starting Pome 0.1.0
2016/01/05 10:33:02 Application will be available at http://127.0.0.1:2345
2016/01/05 10:33:02 sql: Scan error on column index 3: converting string "6.55917056e+08" to a int: strconv.ParseInt: parsing "6.55917056e+08": invalid syntax

Could it be because of our use of bigints?

@amolk
Copy link

amolk commented Jan 5, 2016

+1

@rach
Copy link
Owner

rach commented Jan 5, 2016

I think that's a duplicate of #22 I will have look at it

@kkoch986
Copy link
Author

kkoch986 commented Jan 5, 2016

sorry about that we must have both opened them around the same time

@rach
Copy link
Owner

rach commented Jan 6, 2016

Thanks for reporting it. I think that I may have a fix for this bug. See #22 and b051abf
I'm closing this ticket as it's a dublicate. If this fix solve your problem then I will release 0.1.2

@rach rach closed this as completed Jan 6, 2016
@amolk
Copy link

amolk commented Jan 6, 2016

Thank you Rach! Looking forward to trying out pome.

Best,
Amol

On Jan 5, 2016, at 11:36 PM, Rach Belaid notifications@github.com wrote:

Thanks for reporting it. I think that I may have a fix for this bug. See #22 and b051abf
I'm closing this ticket as it's a dublicate. If this fix solve your problem then I will release 0.1.2


Reply to this email directly or view it on GitHub.

@rach
Copy link
Owner

rach commented Jan 6, 2016

Thanks @amolk . My attempt to fix it was wrong, I found the query which create the error so I should be able to provide a fix a bit later on.

@kkoch986
Copy link
Author

kkoch986 commented Jan 6, 2016

great thanks!

rach added a commit that referenced this issue Jan 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants