Currently, Domo's MySQL is on version 5.6, which is approaching end of support. There are also a number of commonly used features that people want to use in MySQL, but can't because it is still on version 5.6. Please upgrade to the latest version.
I use window functions all the time in redshift, but can't use them in MySQL because they weren't introduced until version 8.0
This needs to get implemented. MySQL 5.6 is over 8 years old. Even the latest version MySQL 8 is 3 years old.
This really needs to move forward.. we need to be able to use CTE to optimize queries.
Any updates for this?
Another significant addition to later versions is the JSON parser! Probably one of the most underrated functions added that would be especially helpful for most of our source datasets coming from connectors that cant flatten nested objects or more importantly, we bring in the data still nested to keep the row count low on each call.
Aside from missing windows and JSON functions in MySQL 5.6 there are security flaws to consider. This is pretty sad that we are still stuck on MySQL version 5.6.37-82.2-82.2. While I realize that Magic ETL is all that there are still a lot of people who find the MySQL dataflows to be their preference.
So I drop my token in the basket to please upgrade MySQL when possible. Hopefully in 2023.
🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏
Any update on this. I also noticed the ppt plugin is on .net 4.5 is this a trend
This would be great!
We absolutely hear this signal on MySQL 5.6. Here are a few thoughts on how we see things:
Updating the status as the SQL Tile for Magic ETL is now in beta. Reach out to your account team to get on the list for the SQL Tile beta.
This must be yet another way that Domo is trying to force us to the consumption model. Otherwise the SQL Tile for Magic ETL is not available (or maybe it is still a BETA product 4 months later!.)
By the way… What SQL parser / engine is used for the SQL Tile? Is it still MySQL 5.6???
I have tried to determine what "flavor" of SQL is used for the dataset views explorer, and have been unable to determine, based on the limited functionality. Hopefully the SQL Tile is NOT using the same.
@BSovers Sorry for any confusion, this is not tied to consumption at all. The SQL Tile is still in beta as we are actively receiving feedback from beta testers and making changes based on that feedback (along with fixing some bugs and making sure the desired features are completed in the tile). It's a very complex feature, and we're taking our time in beta to make sure we're putting something fully baked out to GA. That being said, we've broadened the beta significantly, so if you'd like to join the beta program we could add the tile to your instance.
Re: the flavor of SQL, it is its own Magic-specific syntax. It accepts much of MySQL, much of Redshift, as well as just general ANSII-standard SQL. One notable thing that is not currently available in the tile is window functions (those will come as a follow-on). We did not want to hold the tile back until we got analytic functions, though, so those will not be in the first release. We will have documentation that gives insight into the SQL functionality for the tile, but if you are looking for a super-set of functions that are available in the tile today, you can look at the functions available in the formula writer in the Group By tile (it's a superset of functions from the Formula tile + the aggregation functions from the Group By).
Let me know if you have further questions, or would like to join the the beta for the SQL Tile.
I was just informed by our Account Executive that the SQL Tile will only be available to consumption model accounts, so it does ME no good to try and get into the beta. Though if the "brew-your-own" SQL is all that will be available, then it probably will not be able to do what I need. I need windowing functions, recursive CTEs, etc.. I.e. modern SQL querying!
I get more and more disappointed with Domo every day.
@BSovers I'm sincerely sorry to hear that. I'm getting clarity on why you might have been told it's consumption only, as that is not my understanding. I have sent you a DM and we can chat a bit more about this if you'd like.