MySQL for Developers
41–50 of 119 posts
Re: MySQL for Developers
#42Hey HN, I made this course :D The course is a bit more than 7 hours long split over 64 videos. I was always frustrated by the lack of intermediate database content, it seemed like it was mostly intro stuff, or straight to DBA level. So I read as many database books as I could, read through the official docs, and made this course specifically for application developers. If yall have any feedback I'd love to hear it. I…
This looks great!! Hopefully you can answer a couple questions for me. You mention you're using TablePlus. Doesn't look like it has a free option. Can you recommend another similar database GUI tool so I can "code along"? And is there a database I can connect to and work with? Maybe you answer these at some point in the course, but I didn't see anything in the intro. Also you mention this is for devs and not DBA's. D…
Re: MySQL for Developers
#43Earlier quoted context omitted.
This looks great!! Hopefully you can answer a couple questions for me. You mention you're using TablePlus. Doesn't look like it has a free option. Can you recommend another similar database GUI tool so I can "code along"? And is there a database I can connect to and work with? Maybe you answer these at some point in the course, but I didn't see anything in the intro. Also you mention this is for devs and not DBA's. D…
Table Plus (Free Trial Version) What are the limitations of the free trial? The free trial is limited to 2 opened tabs, 2 opened windows, 2 advanced filters (filters are not available on the free TablePlus Windows) at a time. We can change the limitations without any notifications in the future releases.
Re: MySQL for Developers
#44Cool! Now we need this for Postgres.
Re: MySQL for Developers
#45nice. 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…
MySQL's JSON data type, which exists since 5.7, which is quite old, is a solutely comparable to PostgreSQL's JSONB. (But don't be confused by MariaDB, which is a MySQL fork, where JSON is an alias to MEDIUMTEXT or something like that with little snytax validation)
Re: MySQL for Developers
#46this was both highly anticipated and has been excellently executed. incredible amazing work. thanks Aaron!
Re: MySQL for Developers
#47Does anyone know of a similar intro course for Clickhouse?
Also, be prepared to be blown away with Clickhouse. I've not seen many (any?) technologies that impressed me this much right out the box.
Re: MySQL for Developers
#48Cool! Now we need this for Postgres.
I’ve been using MySQL. Is Postgres so different now that the SQL here won’t work? (It may be that it’s MYSQL that’s different) I know there are some differences in SQL syntax, but in my case we use pretty basic sql…
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?
Re: MySQL for Developers
#49Earlier quoted context omitted.
I’ve been using MySQL. Is Postgres so different now that the SQL here won’t work? (It may be that it’s MYSQL that’s different) I know there are some differences in SQL syntax, but in my case we use pretty basic sql…
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?
If you know the core concepts of one, you are probably 80% good to go with the other.
Re: MySQL for Developers
#50Earlier quoted context omitted.
I’ve been using MySQL. Is Postgres so different now that the SQL here won’t work? (It may be that it’s MYSQL that’s different) I know there are some differences in SQL syntax, but in my case we use pretty basic sql…
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?