MariaDB’s Sequence Storage Engine

The original article was pretty old. It’s been replaced by a news, more complete article I wrote for Vettabase’ website:

MariaDB SEQUENCE: a Simple Approach to Synthetic Data

8 thoughts on “MariaDB’s Sequence Storage Engine

  1. Hello! If you want to use the final count value as a variable parameter, use something like this:

    … FROM (SELECT seq FROM seq_0_to_999999 WHERE seq < 30752) s

    It works well fast, like sets of static strings. Yes, the design is so-so, but usable.

  2. Pingback: FIlling in missing rows in aggregate reports using cardinal numbers

  3. This seems like a really ugly workaround for the fact that MySQL/MariaDB doesn’t support functions that can return a result set.

  4. This is incredibly useful. I’ve always kept a table NUMBERS that I initialized with 0 to 65535, to serve this purpose.
    I assume SEQUENCE is more efficient, although I wonder how it interacts with the query optimizer?

    • Yes, it’s faster because you don’t need to access disk. As far as I understand, it doesn’t need to interact with the optimizer; do you have any example? If you have, I can check for you.

  5. Pingback: MariaDB 10.0 Beta launched – an important milestone « The MariaDB Blog

Leave a comment