Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MySQL for Developers

planetscale.com

Post reply on HN
Print view View original

91–100 of 119 posts

Re: MySQL for Developers

#91

Post by berkle4455 »

ttfkam wrote: post #89

This is excellent. My only gripes have nothing to do with the execution of the training, only the terminology co-opted by MySQL. In MySQL, "schema" means the structure of the whole database. In other RDBMSes, "schema" means a namespace within the database. With its cross-database queries, MySQL puts no distinction between a database and a schema. Once again, not a fault of the training here, but a common source of co…

It's far easier if you view it this way:

* Schema means the same thing on all RDBMS: a namespace for tables

* MySQL doesn't support the notion of multiple databases per server installation

Re: MySQL for Developers

#92

Post by dotancohen »

FinalBriefing wrote: post #49
pphysch wrote: post #48

Earlier quoted context omitted.

Outside of SQL they are different technologies. MySQL mingles its custom language with SQL which is a common point of confusion... Whom amongst us wasn't confused when "DESCRIBE" didn't work in SQLite or Postgres?

Are they really different technologies? It has always been my impression that they are the same tech, but they have a slightly different syntax in some places (DESCRIBE) and different levels of capabilities (Postgres offers more). If you know the core concepts of one, you are probably 80% good to go with the other.

MySQL and Postgres are completely different technologies that are both accessed by a similar interface.

Re: MySQL for Developers

#94

Post by [deleted] »

mulmen wrote: post #87
hu3 wrote: post #86

Earlier quoted context omitted.

Did Uber reverted back to PostgreSQL after switching to MySQL? https://www.uber.com/en-US/blog/postgres-to-mysql-migration/ And as far as I know Netflix was a big Cassandra user then migrated to CockroachDB. I tried to search for "Netflix Postgresql" and found this comment from 2016 stating that they chose MySQL over PostgreSQL: https://news.ycombinator.com/item?id=11950811 Could you share a source?

I just did a few quacks for "companies using postgresql". Tried to keep it to posts in the last couple years. Didn't look too closely. Best source I found is https://www.thomsondata.com/customer-base/companies-that-use... but not sure how current it is.

[deleted]

Re: MySQL for Developers

#95

Post by Implicated »

As someone who has been passively watching you develop and promote this course over what feels like _forever_ - I'm SO excited to see the feedback here the way that it is. Kudos to you and the team at Planetscale, Aaron.

Re: MySQL for Developers

#96

Post by xavdid »

Wow, this looks awesome!

I've really been feeling your "lack of intermediate resources" comment recently. I'm comfortable writing basic SQL queries, but wouldn't know how to set up a new DB and don't really know how to build/structure/optimize/manage a database (outside of tools like the Django ORM, which very helpfully abstracts a lot of it). I've been wanting to get more into SQLite as a starting point, since it seems pretty accessible (as opposed to like, running a server).

Relatedly, I've got an almost-outgrown-Airtable project that I've been considering moving into my own setup, but the 0-to-1 process is pretty intimidating. Plus, Airtable's schema setup I don't think can be replicated 1:1 in SQL (but I'm not even sure that's true).

Anyway, I'm really looking forward to your course. Congrats on the launch, it looks awesome!

Re: MySQL for Developers

#97

Post by kbumsik »

I really wanted to use Planetscale, but there are two blockers:

- No foreign key support

- No CTE support

I tried using Planetscale knowing that there is no foreign key support because it is fine to me. But I had to stop using Planetscale because of the second. My ORM (ent for golang) relies on CTE so I simply cannot run complicated queries.

So if you are considering Planetscale, test it enough especially if you are using an ORM.

Re: MySQL for Developers

#99

Post by ttfkam »

berkle4455 wrote: post #91
ttfkam wrote: post #89

This is excellent. My only gripes have nothing to do with the execution of the training, only the terminology co-opted by MySQL. In MySQL, "schema" means the structure of the whole database. In other RDBMSes, "schema" means a namespace within the database. With its cross-database queries, MySQL puts no distinction between a database and a schema. Once again, not a fault of the training here, but a common source of co…

It's far easier if you view it this way: * Schema means the same thing on all RDBMS: a namespace for tables * MySQL doesn't support the notion of multiple databases per server installation

That's a more charitable way of viewing it. Thank you.
Post reply on HN