BIGINT UNSIGNED value is out of range in '(ua@1 - def@0)' when saving match

[GoogleCodeExporter]

What steps will reproduce the problem?
1.create match
2.put in stats
3.save match

What is the expected output? What do you see instead?

when saving, it gives request succeeded but:
BIGINT UNSIGNED value is out of range in '(ua@1 - def@0)'  appears underneath, 
and the game does not update stats or league points. 

also, if I put any numbers in for tcas for either team the error looks like 
this:
BIGINT UNSIGNED value is out of range in '(`daht_bbl`.`mv_players`.`tcasf` - 
`daht_bbl`.`mv_players`.`tcasa`)'

What version of the product are you using?
9.5 upgraded from 9.1

Original issue reported on code.google.com by Goo...@daht.org on 19 Nov 2012 at 6:36

[GoogleCodeExporter]

also when trying to re-install db back-end procedures in the core panel it 
gives the following error

Notice: Undefined index: bank_threshold in 
/nfs/www/WWW_pages/daht/obbl/lib/class_sqlcore.php on line 1154

Original comment by Goo...@daht.org on 19 Nov 2012 at 5:19

[GoogleCodeExporter]

Have you run all the MySQL upgade commands from the upgrade.php script?

Have you replace the settings files so that new entries are included? (This 
does not seem to be the case??)

Original comment by Nimda...@gmail.com on 19 Dec 2012 at 12:25

[GoogleCodeExporter]

Comment #1 is due to the settings file having been copied over from the 
previous version.

I have looked in the 0.95 code, I can't see why this is happening. I think this 
might be related specifically to your mysql server (maybe in combination with 
obblm).

Anyway, since this only seems to have affected you I'm closing this for now. If 
more reports like this emerge, I'll reopen it as I then might have more 
information on why this is occurring.

Original comment by Nimda...@gmail.com on 28 Feb 2013 at 4:40

• Changed state: Done

[GoogleCodeExporter]

I'm running into the same thing.  I ran 0.9 on Ubuntu 10.04 for a long time.  
That server crashed, so I moved my files over to 12.04.  I restored the 
database, but am running into this issue.  I have deleted the table, rerun the 
install, restored my old mysqldump file, and am still getting the issue.

Original comment by yellowk...@gmail.com on 23 Nov 2013 at 8:50

[GoogleCodeExporter]

I spun up 10.04 in the cloud, repeated the same steps, and it appears to be 
working now.

10.04 mysql version: mysql  Ver 14.14 Distrib 5.1.72, for debian-linux-gnu 
(i486) using readline 6.1

12.04 mysql version: mysql  Ver 14.14 Distrib 5.5.34, for debian-linux-gnu 
(x86_64) using readline 6.2

Could it be a 32 bit vs. 64 bit issue?

Original comment by yellowk...@gmail.com on 26 Nov 2013 at 1:07