Viewing profile — morgo

I work remotely and I've decided that ON is the right choice for me. I made this choice when I started joining a lot of calls where they had to be in English because of me. I figur…

You are correct, it is a disk-format issue, and MySQL officially supports in-place upgrade between versions. It's actually quite hard to fix bugs in charset/collations, because any…

I really like the workflow GitHub uses for this: https://github.blog/2020-02-14-automating-mysql-schema-migra... (It makes use of skeema, which allows you to track your schema in a…

For MySQL there are better ways to do this: https://mysql.wisborg.dk/2018/08/10/innodb-progress-informat... The article is MariaDB specific.

An interesting example to bring up mysql_embedded :-) I was the product manager, and we did have complaints about the size. So it was removed: https://mysqlserverteam.com/mysql-8-0…

If someone uses `utf8` in MySQL 8.0, they will get a warning suggesting they should use `utf8mb4`, because `utf8` will be deprecated. Redefining `utf8` to mean 4-byte would break t…

Hi! Former product manager for MySQL here. The defaults have changed a lot across major releases: https://mysqlserverteam.com/new-defaults-in-mysql-8-0/ https://dev.mysql.com/doc/r…

It should work fine, with one item to note: I believe SqlAlchemy defaults to READ-COMMITTED, whereas TiDB defaults to (and recommends) MySQL's default of REPEATABLE-READ.

Morgan from the TiDB team here. I agree that column and row store have very different characteristics, but what I think is worth mentioning is that some hybrid solutions actually s…

Update: The documentation has now been updated https://github.com/pingcap/tidb/pull/9144

Morgan from the TiDB team here. We are working on at rest encryption now - stay tuned. w.r.t. nested transactions, this is not something that MySQL currently offers (TiDB is MySQL …

Morgan from the TiDB team here. Thank you for the feedback, and I agree with you. We actually took this line out from the same copy in the docs: https://pingcap.com/docs/ (We must …

Hi Rafuino, send me an email at [firstname]@pingcap.com and I'll connect you with the benchmark author. Just to expand a little bit on this comment: > The expected data volume for …

Yes, that is correct. I hope to see FOREIGN KEY constraints added in the future. In the interim though, when comparing TiDB to (application) sharded systems, it is important to cla…

Yes. As a general comment: the component-based architecture lends itself well to adding additional protocols on top. The community has added a Redis protocol on top of TiKV with Ti…

I'll pass this onto the engineering team. Thanks! For a quick answer, I believe Daniel Abadi's followup comment addresses it: > This post did not discuss a central oracle. It discu…

At a high level: - TiDB is Open Source (Apache 2.0 license). Several others that you mention here are commercial offerings. - The expected data volume for TiDB is larger than memor…

To your point: I agree that it pays to be conservative with new filesystems and databases alike. However, I want to mention mitigating circumstances which have helped TiDB stabiliz…

TiDB is an open source NewSQL database that speaks the MySQL protocol. You can scale it horizontally by adding nodes. It is a relational DB (not time series). To describe a couple …

Morgan from the TiDB team here. Happy to answer any questions you have.

I can't speak to PostgreSQL, but I work on the TiDB team having previously worked on the MySQL team. Ensuring compatibility from a clean slate is hard, but to make MySQL distribute…

The technical design for views was recently completed, and I expect to see them added soon :-) Window functions & CTEs are only very recent features in MySQL 8.0 (TiDB is 5.7 compa…

Hi! I work for PingCAP, the company behind TiDB and come from previously working on MySQL. The gap of features missing is documented here: https://www.pingcap.com/docs/sql/mysql-co…

> the percona performance patchset that made it into MariaDB and isn't in MySQL Many Percona patches did make it into MySQL 5.7 and MySQL 8.0.