Login
You're viewing the y.diskcat.com public feed.
  • Oct 31, 2026, 8:02 PM

    I assume the ParticleDB company is going to be doing some damage control PR very soon.

    Your bingo cards might include squares such as

    • we understood the bugs but chose not to reveal the causes to Jepsen
    • our LLMs understand the code fully
    • some bugs were present only in pre-release versions, so they’re fine
    • we were running Jepsen’s published test suite against a different version than the one they ran it on
    • ditto, omitting mention that this was also not a pre-release version
    • ditto, also omitting mention that the version Jepsen tested was a later version, so this was a regression they could and should have caught

    I hope no other DB company is put off hiring Jepsen by this, because if you’re actually competent at database implementation, a database reviewed by Jepsen actually makes you look more competent in the end.

    💬 1🔄 1⭐ 7

Replies

  • Oct 31, 2026, 10:13 PM

    @dpk "WHERE TRUE matched nothing (#35)" 😂

    "Joins … confused similarly-named columns (#77)" 🤯 how the F did they even do that?!? is the database itself an LLM?

    "Inserts ignored provided columns, creating rows best described as “deeply cursed” (#16).¹²"
    "¹²: Jepsen encourages the consistency model research community to come up with more official terms for this.↩︎"

    🤣 :awesome: :thisisfine:

    💬 0🔄 2⭐ 2
  • Oct 31, 2026, 10:18 PM

    @dpk "Strings sometimes turned into eight-bit integers (#37)"

    OH! so THAT'S what happened with #eMudhra|'s keys!

    💬 0🔄 0⭐ 1