Pages: 1
Posted on 05-03-15, 05:35 pm
Death by cuteness

Karma: 6564
Posts: 327/598
Since: 05-01-13
The problem:

And it didn't replace an already existing row, the row somehow managed to duplicate itself! (proved by the fact there are now 327 rows instead of 326)
But the real problem is that it breaks the spritedata.xml file, and you must delete the duplicate sprite 48 manually in the xml file before using NSMBe (this is how I discovered it).

I don't remember how I did it since I though something like that couldn't happen in the first place, so I'm taken by surprise here. The only thing I could think is that I maybe I clicked the Save button twice, and so fast that the DB registered it as 2 separate rows?
Posted on 05-03-15, 07:54 pm
Super Mario
( ͡° ͜ʖ ͡°)

Karma: 9990
Posts: 4276/4457
Since: 06-08-11
What the...??

I think it's a race condition when saving. There were two rows in the table with the same revision number.

Posted on 05-03-15, 08:12 pm
☭ coffee and cream

Karma: 10415
Posts: 1748/2768
Since: 06-26-11
A primary/unique index on id-revision would prevent that entirely
Kuribo64 - RH-fucking-cafe - Kafuka

Posted on 05-06-15, 06:51 am
Super Mario
( ͡° ͜ʖ ͡°)

Karma: 9990
Posts: 4277/4457
Since: 06-08-11
The index was already there but it wasn't unique... Fixed!
Pages: 1