morgo

9 ms·

31.
by morgo 8y ago
I feel just the opposite: emojis are a lot more expressive than text and more universal in language than en-us.
32.
by morgo 8y ago
> Guess what doesn't fit in 767 bytes? VARCHAR(255) in UTF8MB4. Anything above VARCHAR(191) would not be indexable. The utf8mb3 optimization was made before InnoDB was the default storage engine (2010).
33.
by morgo 8y ago
This decision was made before InnoDB was the default. While the performance differences are historical now, consider the case that because of fixed sized buffers, one query could switch from a temp table in memory to a temp table on disk.
34.
by morgo 8y ago
While I agree with you, as I understand the SQL standard defines the N in varchar(N) as characters (not bytes). There is a pathological case which is not common: max length of all 4-byte characters. Indexes are used to enforce features lik
35.
by morgo 8y ago
There are various buffers that were* not variable length in query execution (sorting, temp tables). It is not just about the on-disk format in this case. * Use MySQL 8.0 :-)
36.
by morgo 8y ago
The optimization was made at a different time in history. As I wrote in another comment here: while the decision is regrettable, because of a desire for backwards compatibility and simplified upgrade there wasn't an easy way out of it
37.
by morgo 8y ago
The desire for backwards compatibility/easier upgrades is why utf8mb4 could not just replace utf8: The sorting order for the utf8 collations is not identical to utf8mb4 ones, and so an upgrade would require indexed columns to be rebuil
38.
by morgo 8y ago
Yes - there is a binary collation. w.r.t. arbitrary: The ordering must be deterministic so that indexes can maintain sorted order. It's possible to create a custom collation to have your own ordering - but I would say most users don&#
39.
by morgo 8y ago
Hi! Former Product Manager for MySQL Server here. I have a blog post on this here: https://mysqlserverteam.com/mysql-8-0-when-to-use-utf8mb3-ov... The default for MySQL 8.0 (current GA) is utf8mb4. I also recommend readi
40.
by morgo 8y ago
MariaDB and MySQL have different goals here - MariaDB wants to offer drop-in compatibility for Oracle. MySQL has a core-audience of OLTP apps, that are mostly developed for it specifically. When designing features, I think it's import
41.
by morgo 8y ago
Hi! Former MySQL Product Manager here. I'm not sure I ever looked at this issue specifically, but you are correct: the burden of breaking backwards compatibility should be high, and supported by major use cases. To give a similar exa
42.
by morgo 8y ago
JSON is part of the SQL 2016 standard and exists in other databases as well. I don't see how the trademark is relevant here. I wish we could be more civil and not resort to petty insults. Is there anything I wrote you can dispute wit
43.
by morgo 8y ago
It has both (now). It's a stretch to say Dynamic columns are on the same level. For example, could you index them with virtual generated columns? The syntax is also not as transparent to applications as the ->> JSON operator.
44.
by morgo 8y ago
MariaDB does not have that feature: https://mariadb.atlassian.net/browse/MDEV-4259
45.
by morgo 8y ago
Former MySQL Product Manager here (no longer affiliated). I've been to a Monty talk about this subject, and let me say it was interesting... Monty starts by saying that he does not acknowledge MySQL 5.6's existence since some new
46.
by morgo 8y ago
Former MySQL Product Manager here (no longer affiliated). To cover your specifics: MySQL was first in offering JSON with 5.7. It is still well ahead, for example, there is no JSON_TABLE, aggregate functions, native type or partial update
47.
by morgo 9y ago
The short answer is that it is only single operations that become safer. I don't want to undersell it though: some single operations require multiple steps (i.e. DROP SCHEMA in 5.7 needs to unravel all the tables it discovered and maki
48.
by morgo 9y ago
You are correct - it is currently in RC. The GA release will be a named point release. For example, in 5.7 it was 5.7.9: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/
49.
by morgo 9y ago
We are looking to add something to filter warnings in the future. Thx for the feedback.
50.
by morgo 9y ago
MySQL releases are 2-3 years. So it would be 4-6 years wait in this case :-)
51.
by morgo 9y ago
Product Manager for the MySQL server here. w.r.t. tx_isolation: In MySQL 8.0, it is called transaction_isolation which is the name used by configuration files. MySQL 5.7 supports both names, but now warns when using the old name. Supportin
52.
by morgo 9y ago
I think it's a pretty good policy. Fake reviews/astroturfing comments can hurt a brand quite severely. The riskiest situation of course is talking about a competitor's product (which we kind of are here). It doesn't hav
53.
by morgo 9y ago
Product Manager for MySQL here. Yes, I agree with you that the reason is most likely support. Consider SQL; it's declarative and highly expressive. Your users can craft queries that you did not consider, and you have to make sure the
54.
by morgo 9y ago
I'm the original author of the linked post you refer to. Perhaps the title is click bait, but at the time I was meeting with a lot of users looking for someone else's problems. 5TB could still easily be single server territory. It
55.
by morgo 9y ago
Highest mark: 12/12
56.
by morgo 9y ago
Also Australian in Canada. I sat the mandatory English test, with a number of others that were native speakers. It is a ~$300 test too.
57.
by morgo 9y ago
The content is being re-incorporated in the Doxygen docs, which is generated from the source. (The internals manual was out of date in many cases. I do not recommend relying on the links mentioned here.)
58.
by morgo 9y ago
This is not the MySQL manual (dev.mysql.com) but a third party copy that is at least a few years old. We're working on moving the internals documentation into the server code with Doxygen: http://mysqlserverteam.com/mys
59.
by morgo 9y ago
It has been able to use more than one index per table since MySQL 5.0 (2005): https://dev.mysql.com/doc/refman/5.7/en/index-merge-optimiza...
60.
by morgo 9y ago
It is historical. See: http://mysqlserverteam.com/mysql-8-0-when-to-use-utf8mb3-ove... http://mysqlserverteam.com/sushi-beer-an-introduction-of-utf... (Problem #1) (Author is the first link here.)

More ›