Saltar al contenido principal

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

UNIQUE constraint failed: ZPROCESSHISTORY.Z_PK

Comentarios

1 comentario

  • OddS.

    > Katie Welter: What the hell is this error...

    The answer is technical, long and boring. Are you sure you want to know? In short: The SQLite3 database rejected a value that would duplicate a value already in the very same table column. A duplicate value is not allowed in a column with a unique constraint (imposed by the programmer).

    The more interesting question is what went on before the event that triggered the error. Why did Capture One try to enter a value already in that column? A value Capture One (ok, the programmer) very well knew must be unique. If Capture One crashed, a variant question would be why Capture One (the software) did not properly "catch" the error?

    I would most likely be able to fix my own database, but I can not tell you how to fix yours. You may try the usual route to verify and potentially fix your database in case it got corrupted, or restore from backup, redo some work and try again. You may also try your luck with support.

    0

La publicación no admite más comentarios.