This assumes the code you wrote is already correct and giving the correct answer, so why bother writing tests? If, however you accept that you may have got it wrong, figure out the expected outcome through some reliable means (in this case, dig out your old TI-89), get the result and write your test to assert against a known correct value.
I wouldn't trust any tests that are written this way.
It catches regressions. Which is the one thing where such semi-automated testing is most useful in my eyes.
No clue though why they gave it that weird "expect" name. Basically, it's semi-automated regression testing.
(In my opinion, replicating this via a `validity tstzrange` column is also often a sane approach in PostgreSQL, although OP's blog post doesn't mention it.)
[1]: https://learn.microsoft.com/en-us/sql/relational-databases/t...
This has, at least with current MariaDB versions, the annoying property that you really cannot ever again modify the history without rewriting the whole table, which becomes a major pain in the ass if you ever need schema changes and history items block those.
Maria still has to find some proper balance here between change safety and developer experience.
Sometimes apps will randomly appear to have time limits which the parent has never set also.
It's really a bugfest through and through.
Sorry. Just grumpy, cause I always love the first 80% of his books and then they somehow... just disintegrate.
The real problem is that loads of the wild plant life depends on wild insects, and we do not want to lose that.
Don't get me wrong. Neither I deny climate change, nor do I say we should destroy nature as much as we do.
But we need to start talking the truth instead of invented talking points, or people won't take science serious anymore... even more than they already ignore it.
Everything afterwards felt lame and was geared too much towards multiplayer balance, which does not interest me the least.
Once mod_perl existed (it was late, after lots of CGI perl) - I feel that my clients and I never had significant difficulty in finding providers. PHP was all over the place - it felt - more because there was demand. But there was enough demand for mod_perl that it was always there when we wanted it. We never had to really hunt for a hosting vendor.
Yes, for professional uses. But we lost the next generation of devs. You could put PHP on any shared webspace and people started messing with it and from that messing, the next generation of open source PHP programmers came.
Would rather prefer people would cooperate on ONE fork, e.g. get your extension framework integrated into MariaDB or something.