morgo

20 ms·

151.
by morgo 10y ago
MySQL has done well also. Disclosure: I work on this team. Take a look at new features in 5.7 for example: http://www.thecompletelistoffeatures.com/
152.
by morgo 10y ago
Harrison answered this question here: https://www.quora.com/Is-Facebook-considering-ditching-MySQL... They continue to use MySQL on new projects.
153.
by morgo 10y ago
Yes. Mysqlserverteam.com links usually do not show up on HN, but we have similar benchmarks showing RO throughout to 1.6m qps on Intel
154.
by morgo 10y ago
What you are describing is no longer the default configuration. Say what you like about oracle, they have been a great steward of MySQL.
155.
by morgo 10y ago
lots of things happening in the MySQL world: - a couple of weeks ago we released a document store (new protocol + connectors) based on protobufs - last year 5.7 was released. Many new features, I have a list here: http://www.thec
156.
by morgo 11y ago
As I commented in the parent: it is the default. It was enabled for new installs in MySQL 5.6, and all installs from MySQL 5.7.
157.
by morgo 11y ago
Both of these behaviors you describe are no longer the default in MySQL 5.7 (strict_trans_tables + only_full_group_by).
158.
by morgo 11y ago
> I haven't dug into MySQL for a few years (last I really worked with it was 5.5), but out of the box, it does a lot of things that are pretty unsafe or encourage bad practices, such as truncating data when it's longer than the
159.
by morgo 11y ago
That's not quite correct. It is free if your database is free (using Apache 2.0): http://www.jooq.org/download/
160.
by morgo 11y ago
It also provides validation and is often more space efficient :) the internal format also technically supports partial update, but that is not yet a supported feature. So I wouldn't suggest using text if you are not querying.
161.
by morgo 11y ago
MySQL uses the same lru on text/blob pages as it does other pages - so I don't think it's correct to say it is more likely to go to disk. Demoralization can both help and reduce memory fit depending on the circumstances. You
162.
by morgo 11y ago
Indeed. To expand a little: it has a Json type, functions & virtual columns. So you can extract part of a Json document and index it. The optimizer can also match Json expressions to indexes
163.
by morgo 11y ago
Comparable number is 1.6m on Intel hardware http://www.mysql.com/why-mysql/benchmarks/
164.
by morgo 11y ago
Similar numbers (1.6M) can be achieved with Intel and MySQL 5.7: http://www.infoworld.com/article/2994381/database/mysql-57-d...
165.
by morgo 11y ago
Just to clarify here: The license for MySQL remains the same (GPLv2). It has not changed at any point.
166.
by morgo 11y ago
Author of the list here. Happy to answer any questions you may have.
167.
by morgo 11y ago
This already exists in MySQL (enterprise) here: https://dev.mysql.com/doc/refman/5.6/en/firewall.html
168.
by morgo 11y ago
There are features on both sides which the other database doesn't have. With this specific workload, I think MySQL will work pretty well. Two features in particular: innodb clustered index and compression. (I work on the MySQL team.)
169.
by morgo 11y ago
In MySQL 5.7 this will be possible because there is a native JSON data type + indexing available via computed columns.
170.
MySQL 5.7 will considerably improve defaults(mysqlserverteam.com)
1 points by morgo 11y ago|0 comments
171.
by morgo 11y ago
MySQL of course! (I work on the MySQL team, happy to answer any questions)
172.
by morgo 11y ago
There has been a lot of focus on this for MySQL 5.7. Just take a look at the list of deprecations and changes: http://mysqlserverteam.com/removal-and-deprecation-in-mysql-... We are currently looking into bug 199. The pat
173.
by morgo 11y ago
This is caused by a layering problem in MySQL itself: - Triggers are at the SQL Layer - Foreign keys are implemented natively by InnoDB at the storage engine layer It is not as easy to fix as it sounds.
174.
by morgo 11y ago
There may be some chance that json_* functions become a standard, but have different call parameters. This design allows MySQL to implement both without the backwards compatibility concern.
175.
by morgo 11y ago
One thing that really turns me off is when people talk really negatively about former employees. I met a CTO of a company in Toronto who told me how his predecessor had set up MySQL all wrong. I pressed him for details, and it was not setu
176.
MySQL is 20 years old tomorrow(en.wikipedia.org)
1 points by morgo 11y ago|0 comments
177.
MySQL 5.7 Release Candidate Announced(mysqlserverteam.com)
1 points by morgo 12y ago|0 comments
178.
by morgo 12y ago
I'm curious.. what features are you looking for?
179.
by morgo 12y ago
I'm a non developer working on the MySQL team. One of the ways that I try to help is by collecting feedback from our community of users and passing it back to the developers. Some examples: http://www.tocker.ca/2015&#x2
180.
by morgo 12y ago
This would work great in an office environment. If it's an API, it would be great if there is a chance for an office admin to manage requests as well (i.e. still easier to buy milk from the store; additional coffee cartridges may be i

More ›