Antywzorce sql pdf. Typ danych FLOAT jzyka SQL, tak jak typ danych float w wikszoci jzykw programowania, koduje liczby rzeczywiste w. Antywzorce języka SQL. Jak uniknąć pułapek podczas programowania baz danych. Jan B Karwin. Karwin B., , Antywzorce języka. Antywzorce języka SQL. Jak unikać pułapek podcz Bill Karwin. zł · okladka. Audiobook w mp3; Mobi + Epub.

Author: Nazragore Toll
Country: Montserrat
Language: English (Spanish)
Genre: Finance
Published (Last): 7 September 2006
Pages: 271
PDF File Size: 1.76 Mb
ePub File Size: 7.54 Mb
ISBN: 124-6-55451-576-1
Downloads: 85686
Price: Free* [*Free Regsitration Required]
Uploader: Nern

Antywzorce jezyka sql jak unikac pulapek podczas programowania baz danych bill karwin. Aug 02, Ronald rated it really liked it. A sound coverage of typical SQL schema mistakes, with a useful exposition of the choices available antywzorxe implementing inheritance.

If you’re a developer struggling with database problems, I’d say, pick this book up. I would have appreciated some concrete discussions on writing performant SQL queries. While it chews on the all-known topics nowadays of – ‘readable passwords’ and ‘sql injections’, the ‘pseudokey neat-freak’ isn’t exactly the most popular topic, is it?

Jul 08, Ji rated it liked it Shelves: Improving the Design of Existing Code Refactoring in which every anti- pattern is described following the sntywzorce structure. I enjoyed the discussions around security and can appreciate that storing passwords in the database is a bad idea I’ve seen that more than once and have a better understanding on how to protect against SQL injection attacks.

There is an appendix covering the principles of relational databases, which is useful as a reminder. The book also tries to give examples of when it may be acceptable to use the anti-patterns.

Apr 27, Simon Fermor rated it really liked it. Syntax and some default functions vary based on tools sql server, oracle, mysql.

Now you can stamp out these common database errors once and for all. Some of the anti-patterns I’ve seen before, like not using using constraints or using a column to mean multiple things, but there are many I haven’t seen before but should now be able to spot.

Plsql lets you declare constants and variables, then use them in sql and procedural statements anywhere an expression can be used. His explanation of the problems these can cause should help developers remember why the anti-patterns are so dangerous.


It’s still a good read. What’s most important to read and understand thoroughly is the “Logical Database Design Anti-patterns” chapters.

And if you’ve written the database interface layer for apps, it might be partially interesting for you. May 10, Lisa rated it it was ok. It’s a pretty good book on SQL. The section on application development was a pleasant surprise to me because it talks about testing and possible migration strategies. By explicitly talking about the good parts you can easily figure out if you are in that situation or if you better follow the advised approach.

Also in the sections “regognizing the antipattern” the given examples did sound a bit stupid. Dinged also for nothing on de normalization and what you need to be careful about when doing tbis, after all de normalization can look like an anti pattern. The author definitely could use a different tone and language to get his point across in Beginners will not really understand what’s happening there.

Plsql lets you use all sql data manipulation, cursor control, and transaction control statements, and all sql functions, operators, and pseudocolumns. Harmed with this knowledge, I should not repeat those mistakes and I should have better arguments next time someone in my team is about to commit one. Goodreads helps you keep track of books you want to read.

Paperbackpages. I think this is where people make most of their bad decisions in RDB usage. Developers and DBAs alike would benefit from this read. A great book, that is easy to read, and includes many important topics.

Antywzorce jzyka sql pdf

It’s a nice compendium of practices to avoid with highly memorable titles “Pseudokey neat-freak” is my favoritebut I’m not sure this would be the first title one should read on the subject.

The bad side is that the book is bit bloated, and the last part on application-related anti-patterns doesn’t really fit in. Maybe I’m just lucky to work on things that were well built or I’m more experienced than the target audience for the book.

I also enjoyed the comparison of the Active Record pattern versus the Repository pattern as it convinced me that the decision to use Repository on my current project was a reasonable one. Zapytania jezyka sql skladaja sie z wyrazen jezyka przetwarzania danych, jak select, update czy delete. As of late, I’ve been letting Hibernat I’m a software developer who gets paid mostly for working on the back end portion of solutions and I’ve worked in both small and large companies.


Very well written – concise and to the point text interspersed with both SQL and general software development bits of wisdom, followed by simple but not simplistic examples.

Want to Read Currently Reading Read. Plsql stands for procedural language structured query language.

Books by Bill Karwin. I regret that I did not read it before, because it will resolve some of issues during my work. The author uses good, real world, examples written in clear language.

Antywzorce sql pdf

A very good book for younger developers, but I’ve learned most of these solutions already so I wanted a bit more out of this book. It stored and compiled in the database, runs within the oracle executable and inherits the security, jzjka and portability of the oracle database. If in one way or another you are involved with databases you should read this book.

Even better, it explains in dept why they are errors and the problems you might This books describes common errors developers make when dealing with databases.

Chapter 24 “Diplomatic Immunity” is a worth to be part of Robert C. Jan 18, Bill rated it liked it.

Most antipatterns are about misunderstandings on good database design; for example, the author discusses such timeless classics as implementing many-to-many relationships by putting multiple comma-separated values in a row. More times than not, however, the development team atnywzorce to craft the SQL ourselves.

All in all, a decent read for a new SQL user, but if you have any experience with SQL you might want to skip this one for a newer reference.