4 ms·

Mysql for some reason still lacks: * uuid type * datetime with timezone * storing (and retrieving) the view definition as it was defined with comments, forma

by nvivo 9y ago

Mysql for some reason still lacks: * uuid type * datetime with timezone * storing (and retrieving) the view definition as it was defined with comments, formatting, etc * using the same temporary table multiple times in the same query This is not an extensive list, but are things that bite me every day with mysql. Even though it's not query cache related, I wonder why such basic features are still missing and what are the plans to include them? They sound much simpler and more important to add than adding a nosql protocol to a sql database.

morgo 9y ago
I'm not sure if that was a question, but I'll answer :-) * For UUID, we've added helper functions to store it in insert-friendly order: http://mysqlserverteam.com/mysql-8-0-uuid-support/ http://mysqlserverteam.com/mysql-8-0-uuid-support/ * For Datetime + Timezone, this is something we are looking into currently. Datatypes are actually not simple to add in MySQL. While STRICT mode is the default, we support the upgrade case of it disabled. Which leaves us with a number of implicit conversions to handle. I wish it wasn't the case, but it's not be lack of demand on our side :-) We intend to schedule refactoring work to make this easier in the future. * For storing/retrieving view definitions I hear you on that one. There is a documented reason though: > The advantage of storing a view definition in canonical form is that changes made later to the value of sql_mode will not affect the results from the view. However an additional consequence is that comments prior to SELECT are stripped from the definition by the server. * Re-using the same temporary table can now be worked around with a CTE (8.0), which is preferred. It is not just a case of prioritization, but also resourcing. We have a large team, and have different people working on data types from protocol work :-)

by nvivo 9y ago

morgo 9y ago

I'm not sure if that was a question, but I'll answer :-) * For UUID, we've added helper functions to store it in insert-friendly order: http://mysqlserverteam.com/mysql-8-0-uuid-support/ http://mysqlserverteam.com/mysql-8-0-uuid-support/ * For Datetime + Timezone, this is something we are looking into currently. Datatypes are actually not simple to add in MySQL. While STRICT mode is the default, we support the upgrade case of it disabled. Which leaves us with a number of implicit conversions to handle. I wish it wasn't the case, but it's not be lack of demand on our side :-) We intend to schedule refactoring work to make this easier in the future. * For storing/retrieving view definitions I hear you on that one. There is a documented reason though: > The advantage of storing a view definition in canonical form is that changes made later to the value of sql_mode will not affect the results from the view. However an additional consequence is that comments prior to SELECT are stripped from the definition by the server. * Re-using the same temporary table can now be worked around with a CTE (8.0), which is preferred. It is not just a case of prioritization, but also resourcing. We have a large team, and have different people working on data types from protocol work :-)