Problem with the Arcade.

[Sonicboy 101]

Everytime I play a game and submit the score, it comes up with a SQL error. I was up to getting some high scores too, Snake for one.
Anyone else having the same problem, or is it just me?
(Didn't know where to post, so I just posted here. )

[SnesR0X]

Well if you look here http://www.dcemu.co.uk/vbulletin/showthread.php?t=87138
I've had the same issue.

[Sonicboy 101]

Ok, I didn't see that thread.

[VampDude]

Yeah, quite a few of my scores haven't gone through lately...

...Me personally, I don't worry about if my score cannot be submitted as I can keep playing and when the scoreboards are all working properly I can then play and submit my scores which may be better that a score that wasn't submitted

[bah]

Same for me, it looks like the primary ID is set as a signed 32bit integer and its run out of digits to increment/assign.

"mySQL error: Duplicate entry '2147483647' for key 1"

Otherwise that number is an awful coincidence.

[VampDude]

Same for me, it looks like the primary ID is set as a signed 32bit integer and its run out of digits to increment/assign.

"mySQL error: Duplicate entry '2147483647' for key 1"

Otherwise that number is an awful coincidence.

I get that message quite a lot, especially when I beat "Who Wants To Be A Millionaire" because the $1,000,000 score has already been taken! (by Kcajblue) lol

[bah]

Its giving an error on a column that is required to be unique (scores dont need to be unique) at the exact number that is the limit of the signed 32bit integer data type (Signed: −2,147,483,648 to +2,147,483,647). I thought it would wrap around to a negative but I'm wrong obviously.

That number doesn't exist in any of the fields listed in the error so I'm assuming its the rows Primary ID and its hit its limit for that data type.

[VampDude]

Its giving an error on a column that is required to be unique (scores dont need to be unique) at the exact number that is the limit of the signed 32bit integer data type (Signed: −2,147,483,648 to +2,147,483,647). I thought it would wrap around to a negative but I'm wrong obviously.

That number doesn't exist in any of the fields listed in the error so I'm assuming its the rows Primary ID and its hit its limit for that data type.

Hmmm?

[bah]

??
The error it gives me every time is:

mySQL query error: INSERT INTO games_scores
(mid,gid,name,score,ip,timespent,datescored,commen t) VALUES
('16751','110','bah','870','202.168.98.214','126', '1201156710','')

mySQL error: Duplicate entry '2147483647' for key 1
mySQL error code:
Date: Thursday 24th of January 2008 07:38:30 AM

It cannot create the entry because the figure 2147483647 already exists in the table in a field that has to be unique.
You reference information in a database by a unique identifier for the row, often it is a number automatically generated by adding 1 to the previous entry's number as it doesn't matter what it is, as long as it is unique.

The fact that the number it is trying to repeatedly insert is the exact upper limit of the 32bit signed integer data type makes me think that the cause is that it cannot enumerate (+1) to the number and hence cannot add new entries to the table because of it.

I could be wrong, its just an awful coincidence.

[VampDude]

??
The error it gives me every time is:

mySQL query error: INSERT INTO games_scores
(mid,gid,name,score,ip,timespent,datescored,commen t) VALUES
('16751','110','bah','870','202.168.98.214','126', '1201156710','')

mySQL error: Duplicate entry '2147483647' for key 1
mySQL error code:
Date: Thursday 24th of January 2008 07:38:30 AM

It cannot create the entry because the figure 2147483647 already exists in the table in a field that has to be unique.
You reference information in a database by a unique identifier for the row, often it is a number automatically generated by adding 1 to the previous entry's number as it doesn't matter what it is, as long as it is unique.

The fact that the number it is trying to repeatedly insert is the exact upper limit of the 32bit signed integer data type makes me think that the cause is that it cannot enumerate (+1) to the number and hence cannot add new entries to the table because of it.

I could be wrong, its just an awful coincidence.

Hopefully it will get fixed soon...

...Anyway your not as unlucky as me, I was playing Roulette earlier and winning but not being given my wager returns so I ended up losing all my money

Here's a video of the last $10 I lost at Roulette, which should've been turned into $20 (below) that turned to $0.