Romcenter

When I update a database (from a datafile), from time to time the database gest corrupted.

When this happens, after "Loading gameslist" I get the following error message:

arithmetic exception, numeric overflow, or string truncation
Arithmetic overflow or division by zero has occurred.
Error Code: 1
Database closed

At that point, the only option I have is to delete the database and create it again from the datafile. Trying to reopen the corrupted database will simply result in the same error message.

I'm currently using Romcenter 3.54 but the problem has been present within the last few releases.

Thank you for reporting.

Could you give me the name of a datafile which raise the error?

I update my Nintendo DS database a few times a week from the dat file at no-intro.org

http://datomatic.no-intro.org/

Since it's the one I update the most often, it's usually the one database that gets corrupted. It has happened before with the MAME database from Logiqx too but since it doesn't get updated as often it's pretty rare that it gives me any trouble. I haven't been able to figure out anything particular about the times the database gest corrupted versus the rest of the time. It just seems to happen randomly.

I have the same problem as Zomby reports. I also use dat files from http://datomatic.no-intro.org/.
For me too it seems to happen randomly.
I always make backups of my databases. When i open an older database i can usually update this one
with the latest dat-file so i do not have to rebuild a database from scratch.

I tried with the following dat from no-intro: (loading one, updates to another one etc...)
Nintendo - Nintendo DS Decrypted (20110102_RC).dat
Nintendo - Nintendo DS Decrypted (20110102_CM).dat
Nintendo - Nintendo DS Parent-Clone (20110102).dat

I didn't meet any problem.

Do you have roms paths loaded in rc when the problem occurs ? Could it come from a rom file ?
Can you reproduce the problem with one of these files ?

I can now reproduce the problem. It will be fixed in next release.

Great news!

I'm glad to see you managed to reproduce the problem. Could you shed any light on what it was?

It was a bad field format in a database view. It was defined as smallint instead of integer, and when a game id exceed the max value of smallint (32768), it throws an overflow error.