Earlier quoted context omitted.
The Art of Postgres is probably it. https://theartofpostgresql.com/
The Art of Postgresql is a book not a video course And unfortunately they dont provide to table of content on the site
MySQL for Developers
71–80 of 119 posts
Re: MySQL for Developers
#72Re: MySQL for Developers
#73This is perfect I was looking for something like this will definitely be checking it out over this weekend one request please give us the training data set you use for this course so that we can follow along with all the sql queries you are typing.
Re: MySQL for Developers
#74Earlier quoted context omitted.
The Art of Postgresql is a book not a video course And unfortunately they dont provide to table of content on the site
Also, while we may see $75 or $150 or whatever as throwaway money (especially in the context of professional help products or books), that price is wildly unaffordable for most of the planet. Having high-quality free educational material out there is a godsend for students and developers in low income countries.
But also your point of students and developers in low income countries completely understand that side. It's a shameless plug but we built our Postgres playground with tutorials on a number of topics which are completely free aiming to help target some of that audience - https://www.crunchydata.com/developers/tutorials
Re: MySQL for Developers
#75nice. i use MS SQL at work and MySql for personal project
Might be worth looking into PostgreSQL as well. It's just as readily containerized (docker) as well as being more ANSI compliant and consistent. I only say this because nearly every time I've ever used MySQL, I find annoyances. Such as the fact that 'utf8' isn't 'utf8', 'utf8mb4' is... the feature was in testing as utf8 was being standardized and mysql used 'utf8mb3', and never updated the reference for 'utf8' for co…
Nothing like trying to do a select on a table/column that you know is there and getting an error...becuase the table/column was created with quotes by your ORM so it doesn't automagically get case in-sensitized.
It's maddening.
Re: MySQL for Developers
#76Re: MySQL for Developers
#77It's really nice to see more content for MySQL/MariaDB still being made, since it feels like they are still good solutions for a whole variety of situations! While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough!
I see this sentiment often here on HN. Something long the lines of "MySQL is enough for small apps but you want PotgreSQL for serious work."
When in practice I find the opposite to be true. PotgreSQL is hard to scale and hard to upgrade when compared to MySQL. I mean, just take a look at the caliber of companies that leverage MySQL at scale using Vitess to orchestrate it (spoiler, it powers Youtube, GitHub, Slack, Shopify and more):
https://planetscale.com/vitess
What's PostgreSQL comparable list?
Re: MySQL for Developers
#78Earlier quoted context omitted.
Might be worth looking into PostgreSQL as well. It's just as readily containerized (docker) as well as being more ANSI compliant and consistent. I only say this because nearly every time I've ever used MySQL, I find annoyances. Such as the fact that 'utf8' isn't 'utf8', 'utf8mb4' is... the feature was in testing as utf8 was being standardized and mysql used 'utf8mb3', and never updated the reference for 'utf8' for co…
PosgreSQL has its share of annoyances, like case preserving case insensitivity and inconsistent naming of its tools/config files. Nothing like trying to do a select on a table/column that you know is there and getting an error...becuase the table/column was created with quotes by your ORM so it doesn't automagically get case in-sensitized. It's maddening.
Re: MySQL for Developers
#79It's really nice to see more content for MySQL/MariaDB still being made, since it feels like they are still good solutions for a whole variety of situations! While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough!
Further "evidence" by referring to other experienced folks who worked on scaling SQL databases, and MySQL is what's used and what folks have experience with:
- https://twitter.com/Sirupsen/status/1602347646961606656
- https://blog.nelhage.com/post/some-opinionated-sql-takes/#my-personal-choice-mysqlRe: MySQL for Developers
#80It's really nice to see more content for MySQL/MariaDB still being made, since it feels like they are still good solutions for a whole variety of situations! While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough!
> While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough I see this sentiment often here on HN. Something long the lines of "MySQL is enough for small apps but you want PotgreSQL for serious work." When in practice I find the opposite to be true. PotgreSQL is hard to scale and hard to upgrade when compared…
Netflix, Instagram, Spotify, Skype, Reddit, Twitch, Yahoo.
e: removed Uber.