https://bugzilla.wikimedia.org/show_bug.cgi?id=42325
Daniel Kinzler <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Daniel Kinzler <[email protected]> 2012-11-26 23:49:57 UTC --- We should look whether the uniqueness check is done on the master database - if not, the conflict would not be detected before saving. Then, the item's primary data blob would be saved with the conflicting info, and only the secondary database update would cause a unique key error. I can imagine the above scenario - but not really with a delay of 30 minutes. Slave lag just doesn't get that high. Anyway: merl, can you check whether the request that created the second entry actually returned ok, or whether it returned a fatal error of some sort? -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
