Page 1 of 1

Division by zero

PostPosted: Wed Feb 27, 2008 12:05 am
by mdesjard
When I try to access the data from one of my older alias (on Empire Poker from 3 years ago). I get a SQL error in the main window.

It says "Unable to execute query: SELECT htts.id_limit... ; Reason: Fatal Error (ERROR: division by zero)"

I didn't paste the whole SQL query, let me know if you need more info.

Thanks

Re: Division by zero

PostPosted: Wed Feb 27, 2008 12:46 am
by Josh
If you can narrow it down to a group of hands or sessions, or anything to get us a hand history that's causing the problem, that would be helpful.

Re: Division by zero

PostPosted: Thu Feb 28, 2008 9:17 pm
by mdesjard
Done, I've narrowed it down to one file history. I've submitted a bug with the file as an attachement.

Seems like it's a tournament file history but it's affecting the information in the cash game tab.

Re: Division by zero

PostPosted: Thu Feb 28, 2008 10:26 pm
by Josh
Then PT3 is likely not recognizing it as a tournament hand. I'll take a look at the hand history and get this fixed.

Re: Division by zero

PostPosted: Fri Feb 29, 2008 12:33 am
by APerfect10
I was unable to replicate this problem with your hand history file that you submitted. I forwarded it to Josh to review...

-Derek

Re: Division by zero

PostPosted: Fri Feb 29, 2008 5:21 am
by WhiteRider
I've had cases like this when testing, where I found a problem with a HH in my main DB but couldn't reproduce it with a single hand.
mdesjard, try creating a blank new database and importing just that single hand history and see if you still get the problem.

Re: Division by zero

PostPosted: Fri Feb 29, 2008 11:07 am
by mdesjard
Hi,

Here's what I did, I imported my hand histories 30-50 files at a time until I saw the error. Once I saw it, I purged my DB and then imported 10 at a time. when I saw the error again, I purged once again and then imported one file at a time.

Once I narrowed it down to a single file. I purged once more and imported only that one file and I got the error.

I'm using postgres 8.3 if that makes a difference...

highfalutin