Why we're ending support for MySQL
I mean, I&#x27;m not too upset that they&#x27;re focusing on one DB engine, but their reasons are a bit facetious.<p>&gt; There are lots of great use cases for MySQL, our specific needs just didn&#x27;t seem to be a good fit. Our use of MySQL had a number of limitations. In most cases, it wasn&#x27;t as simple as adding support to MySQL, but that by bending MySQL we typically broke PostgreSQL. To name a few limitations:<p>&gt; We can&#x27;t support nested groups with MySQL in a performant way<p>All they had to do was implement a nested set pattern for their groups [1]<p>&gt; We have to use hacks to increase limits on columns and this can lead to MySQL refusing to store data<p>A hack? Their DB creation schema specified a TEXT column when it should have been a LONGTEXT column. Using LONGTEXT is not a hack, it&#x27;s a choice when your data is more than 65535 characters, and they made the wrong choice out of ignorance.<p>&gt; MySQL can&#x27;t add TEXT type column without length specified<p>That&#x27;s just incorrect. What they MEANT to say is that they had a column to store filenames that was a varchar(255) column and people were running out of space with long directory paths and filenames. They could have moved to a TEXT column, but didn&#x27;t because they thought it couldn&#x27;t be indexed without specifying a length... But they were wrong, you CAN index a TEXT column without specifying the TEXT column length, you just have to specify the length of the substring you want to index.<p>Alternatively, since this is filepaths and filenames, they could have used a nested set pattern again and gotten 255 characters for each component of the path and a lot more feature options for their search system!<p>&gt; MySQL doesn&#x27;t support partial indexes<p>This is true, but is it really a show stopper?<p>&gt; As a side note – we don&#x27;t use MySQL ourselves<p>I think this is the real reason. They just didn&#x27;t have the necessary talent to implement the features correctly. Wrong schema specifications and not knowing to implement nested set patterns is a sign that they don&#x27;t have a knowledgeable DBA on staff.<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Nested_set_model" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Nested_set_model</a>