Moreover, their sequence example for the relational database is just plain the wrong way you would go about that. In the relational example they give[1], that

Moreover, their sequence example for the relational database is just plain the wrong way you would go about that. In the relational example they give[1], that is how you'd capture "have they done X, Y, and Z" whereas the sequence is explicitly capturing the order those things were done in. If you care about that information, you would design your system for this. The point could have been that this is actually simpler with sequences, not that it's impossible in a relational db. We already have loads of examples of how to capture this data and put it in order. But I suppose a table with a User, Action, and Timestamp column would really invalidate the point the author was trying to make. Then it's just a select and order by to get the order things happened in. [1]: https://miro.medium.com/max/1026/0*NbWYw7bbEflgG-5m https://miro.medium.com/max/1026/0*NbWYw7bbEflgG-5m