3 ms·
>4. I don't find myself needing many SQL features beyond the basics. That's probably why you still like it. As it stands, MySQL has so many shortcomings it's n
by kidmenot 12y ago
>4. I don't find myself needing many SQL features beyond the basics.
That's probably why you still like it. As it stands, MySQL has so many shortcomings it's not even funny.
Version 5.7 is the first one to support multiple triggers per event. Beyond that, and just to name a few, you can't have subselects in views, you don't have CTEs (good luck storing hierarchical data in an adjacency list), no materialized views, CHECK constraints are parsed but ignored.
I'm glad it works for you, but the minute you need to do something slightly more complex, MySQL gets in your way.
I hope the situation will improve, though.
- Buttons840 12y agoThere have been several times in my career where I have missed full SQL support in MySQL databases other people have setup and left for me to maintain. Choosing MySQL isn't the worst thing one can do when building a new system, but just because the initial designers don't intend to use advanced SQL features doesn't mean future use cases wont benefit from full SQL support.
- kidmenot 12y agoIndeed. Just these days the lack of materialized view has been giving me troubles. It would make a certain process about 50 times faster without touching code at all, and it would take me all of three queries. Granted, the real problem is a poor design of the system, but materialized views would enable me to improve what others have left behind.