# CardinalityViolation exceptions, database corruption?

**URL:** <https://meta.discourse.org/t/cardinalityviolation-exceptions-database-corruption/140713>\
**Category:** Product Support\
**Tags:** unsupported-install\
**Created:** [February 5, 2020, 11:46am UTC](https://meta.discourse.org/t/cardinalityviolation-exceptions-database-corruption/140713 "2020-02-05T11:46:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![barthalion](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@barthalion](https://meta.discourse.org/u/barthalion)\
**Post date:** [February 6, 2020, 1:30pm UTC](https://meta.discourse.org/t/cardinalityviolation-exceptions-database-corruption/140713/5 "2020-02-06T13:30:03Z")

</div>

Thanks a lot. Started poking around database some more and it’s clearly corrupted. Many posts had the same post\_number or sort\_order, there were also IDs visible via `select * from posts where topic_id = x` but not if I added `and id = y`.

@Jeff, I’ve never said I don’t understand your decision! I wouldn’t ask for help if it was anything deployment-specific.

---

_[View the full topic](https://meta.discourse.org/t/cardinalityviolation-exceptions-database-corruption/140713)._
