Learn SQL Database Programming

Me agrado mucho este articulo.

This isn't a bad book - it's actually pretty good. It's just not what the title claims. This book is good a good buy for 1 of these 2 use cases:1) You're brand new to using a real database (Excel and Access don't count), and you want a high-level introduction to using MySQL and writing SQL queries, etc.2) You're quite good with SQL and databases already, and you just want a reference on your desk you can flip open to check the syntax on part of your query, or similar reference-type needs.Besides that, I think this book is a miss. It's covers a lot of ground, but it moves really fast, and barely anything goes into much depth. As a result, if you're new to SQL then you won't actually *learn* much here (there are too few examples, and they never go into much depth) – but if you're a pro this is all pretty obvious, so you won't learn anything new.My main other complaint about this book is that for a book with "Programming" in the title, it barely meets that standard at all. Besides a quick pass on functions and stored procedures (which do involve programming via SQL), almost everything this book does is via the MySQL Workbench tool. Now, that's great if learning Workbench is your goal - but if you want to manage your database via APIs, or do anything programmatic whatsoever (via a language like Python, Java, etc.), this book has ZERO on ANY of that. The work "Programming" has no place in the title of this book.Two other minor complaints:1) There are some sloppy typos and technical errors that should have been caught by the editors - and that happened a couple times too many for me to ignore.2) The book really feels like the author was trying to pad the page count. There are a TON of screenshots (again, mostly of MySQL Workbench). While I usually like those, for reference, they were larger and more frequent than necessary. There are also pages of content that get very repetitive - like, the author would often repeat the same exact paragraph multiple times when explaining a list of things that were mostly the same, but had only slight differences. (for example, a full paragraph explaining an example with a logical TRUE/IN/= use case, and then the exact same paragraph repeated again but with just a couple words changed to explain the respective FALSE/NOT IN/!= use case). Pages of text could have been saved by using a more compact writing approach.All that said, this is a pretty good book for the 2 needs I mentioned at the top of this review. If that's you, buy it and make the most of it. But anyone wanting to really learn how to "program SQL" will need to read a few other books, too. Now you know.

Nachdem ich von einem anderen Buch des Packt-Verlag (C#9 and .net5 modern cross-platform development) echt angetan war, habe ich mir dieses Buch gekauft. Leider muss ich sagen, dass dieses Buch ein Ärgernis ist.Ich bin gerade mal auf S.115 und schon über so viele Fehler gestolpert, dass es mir echt vorm Rest des Buches graust.Ein paar Beispiele: S.18 "the primary keys ensures that all values in a column are not null and UNIQUE..." Auf S.29 wird dann anhand einer Tabelle behauptet, dass die Kombination aus playerID and teamID einen Primary key ergeben. In Zeile 2 dieser Tabelle steht: abreubo01 (als playerID) und PHI (als teamID), in Zeile 3 steht das selbe. Man müsste die yearID noch mit dazu nehmen, um einen primary key zu erhalten, was auf S.17 auch schon mal festgestellt wurde.Auf S.114 im Abschnitt many-to-many table relationships wird im Text dann fälschlicherweise von einer one-to-many geschrieben.Dazu kommt noch, dass die Seiten teilweise wirklich mit belanglosen Informationen zugemüllt wurden. Die Autorin hat sich entschieden MySQL zu benutzen, dann möchte ich nicht auf jeder Seite zu Datentypen lesen, wie sich das von anderen Datenbanksystemen unterscheidet, dass kann man einmal als Info erwähnen und in einem Anhang kompakt auflisten. Dann ist das Kapital halt nur 10 statt 20 Seiten lang.Hingegen wird man im Kapitel 2 aufgefordert eine Datenbank von GitHub runterzuladen, wo man eventuell anhand eines Screenshots oder erläuterten Text erklären könnte, wie das funktioniert (Google hilft weiter).Das alles ist kein Beinbruch und man kann sich sicherlich auch anhand dieses Buches einen Zugang zu SQL erarbeiten, aber es gibt keinen Grund dieses Buch zu nutzen, da es ziemlich sicher bessere gibt.