[ffsm8]

Eh, most people would like their apps to provide them with a browsable history of their data, and why the changes happened.

It's just increases scope x100 to get anything done, so few do it... but if the tooling was available, almost all stateful applications would benefit from it.

[Demiurge]

Most people? There is a Django-history module, and yet it’s not nearly as popular as Django. I’ve used this on two out of 100 projects. No one ever actually wanted the history, it’s there for “just in case of an audit” and compliance, which never comes.

[wordofx]

lol no. And the DB isn’t going to tell you who what why without you writing code to support that audit in which case… that special database has solved exactly 0 problems that a traditional RDBMS already solves.

[ffsm8]

I was addressing the point "nobody wants that". And I disagreed, because: if it existed, almost everyone would want it.

The tooling just doesn't exist. Doing it with half-assed tooling increases the scope of literally every development you'd be doing, so nobody bothers with it. Ive never worked with this particular database, so no idea how it would work in practice here.