Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
morgo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
181.
▲
by
morgo
12y ago
This looks similar* to replication w/GTIDs + transactional replication (both MySQL 5.6 features). * MySQL replication works a little different by using binary logs.
182.
▲
by
morgo
12y ago
Small clarification: > If you specify ALGORITHM=INPLACE,LOCK=NONE you can alter table without blocking reads and writes. We have used this method successfully in Amazon RDS when updating schemas. The use-case of ALGORITHM=INPLACE and LOC
183.
▲
by
morgo
12y ago
This is noted in the release notes, and I have a blog post on it here: http://www.tocker.ca/2015/03/10/heads-up-mysql-5-7-dmr6-cont... To describe our process: We have at least 2 code reviews, ~90% test cover
184.
▲
by
morgo
12y ago
See my other comment in this thread RE: string truncation (strict sql mode will default on in MySQL 5.6/5.7). It is possible to change timestamps to default to Null. For backwards compatibility, the previous behavior defaults: http:&
185.
▲
by
morgo
12y ago
This is indeed the case. To clarify a little: - STRICT_TRANS_TABLES is on by default for "new installations" starting from MySQL 5.6 (2013). What this means is that the bundled config files all turn it on. - Starting from MySQL
186.
▲
by
morgo
12y ago
Being able to change it on a per connection basis is required for earlier applications. If we use Wordpress as an example, upon initial connection it will set the SQL mode to what it is compatible with (magento, drupal, others also do simi
187.
▲
by
morgo
12y ago
I totally hear you here :) Visibility is the most useful and always under-rated feature. If I can clarify some of the recent enhancements here: - MySQL 5.6 introduced `EXPLAIN FORMAT=JSON`. MySQL Workbench uses this to visualize query
188.
▲
by
morgo
12y ago
If you do not like explain, may I suggest using `EXPLAIN FORMAT=JSON` - it is new to MySQL 5.6, and contains additional meta data. There is also optimizer trace, which provides significantly more meta data. Some good examples in these sli
189.
▲
by
morgo
12y ago
I like it - thanks for the link.
190.
▲
by
morgo
12y ago
Yes. See slide 43 for examples of statements that now produce errors by default: http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 This will break some applications that are upgrading. I have a whitelist&#
191.
▲
by
morgo
12y ago
MySQL 5.6 supports Online DDL. Most operations are online, you can see a list at: http://dev.mysql.com/doc/refman/5.6/en/innodb-create-index-o... (The table 14.5 column "Allows Concurrent DML?"
192.
▲
by
morgo
12y ago
Please see my comments on this thread: https://news.ycombinator.com/item?id=8318199 I agree it's a silly name, but it's not like we created it :)
193.
▲
by
morgo
12y ago
1. We're working on something in this area: http://mysqlserverteam.com/generated-columns-in-mysql-5-7-5/ 2. InnoDB has fulltext from MySQL 5.6+ 3. I agree utf8mb4 should be renamed "utf8". When this was
194.
▲
by
morgo
12y ago
Edward Screven addresses this point in this video: https://www.youtube.com/watch?v=fzCpd4j72jA - Oracle sees MySQL users as a distinct group of customers from the Oracle Database - 5 years on, the engineering team on MySQL
195.
▲
by
morgo
12y ago
5.7.6 is what we call a "Development Milestone Release", and is stated to be of approximately release candidate quality. We do not have a release date, but we're committed to a 2-3 year release cycle, with 5.6 being the last
196.
▲
by
morgo
12y ago
In the context of this post (MySQL 5.7) it does not accept invalid data :) The default sql mode has changed.
197.
▲
by
morgo
12y ago
Under your point (3), it is important to note that this has been a major focus area of MySQL. I have two comments to make on it: 1) Peak throughput is not as important as consistent throughput (i.e. less variance between response times).
198.
▲
by
morgo
12y ago
Community Manager for MySQL here! A better overview link for what's new in 5.7.6 specifically is this one: http://mysqlserverteam.com/the-mysql-5-7-6-milestone-release... To understand what's new in 5.7 overall:
199.
▲
by
morgo
12y ago
I would say the biggest change is that the default SQL mode will be the equivalent to 5.6's ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER. Thi
200.
▲
by
morgo
12y ago
Checkpoint and vacuum are good examples. There are other stalls we have had to address: extending the size of tablespace files, dropping tables and scanning the LRU to free pages.
201.
▲
by
morgo
12y ago
I appreciate the straight-forwardness of this comment :) One of the things that I think would be interesting to show, is how the consistency of performance has improved over time too. There has been a lot of focus on removing any stalls in
202.
▲
by
morgo
12y ago
It is supported, just not in XML dump format.
203.
▲
by
morgo
12y ago
Easiest way is probably to run a HEX() function on the column, and compare output.
204.
▲
by
morgo
12y ago
I totally agree! It also makes sense for countries that have their own character sets to use utf8 too (as they may borrow words, characters from other languages). I was just pointing out that even if it was limited support, it wasn't
205.
▲
by
morgo
12y ago
To clarify: the 3-byte subset is not a MySQL invention. It is the Basic Multilingual Plane (BMP): http://en.wikipedia.org/wiki/Plane_%28Unicode%29#Basic_Multi...
206.
▲
by
morgo
12y ago
This appears to be a tool for generating test data, for your application. For testing SQL database engines there is the Random Query Generator: https://launchpad.net/randgen It was designed for MySQL, but works fine with ot
207.
▲
by
morgo
12y ago
And MySQL Fabric: http://dev.mysql.com/doc/mysql-utilities/1.4/en/fabric.html
208.
▲
by
morgo
12y ago
Totally agree. Or in some cases: Product Manager or Technology Evangelist.
209.
▲
by
morgo
12y ago
I am a Community Manager (for MySQL at Oracle). I don't find anything particularly offensive with what Aaron has to say. The scenarios are certainly all possible... but I don't think I've ever seen a CM pull rank and say &qu
210.
▲
by
morgo
12y ago
Technically, it was introduced in 5.5, but off by default :) 5.7 is going to be amazing for observability. Memory, transactions, stored procedures, replication, meta data locking and prepared statements are all instrumented in P_S.
More ›