On Tue, 3 May 2016 23:11:06 -0500 Guyren Howe <guyren@xxxxxxxxx> wrote: > I've long been frustrated with how most web developers I meet have no idea how to use an SQL database properly. I think I'm going to write a book called Love Your Database, aimed at web developers, that explains how to make their apps better by leveraging the power of SQL in general, and Postgres in particular. > > I'm thinking of a section on features of SQL most folks don't know about (CTEs are *way* to hell at the top of that list, but also EXCEPT/INTERSECT and window functions), but much of the book would be about how to do things server side. Benchmarks showing how much faster this can be, but mostly techniques ? stored procedures/triggers/rules, views. > > I asked a colleague about the advice I often hear stated but seldom justified, that one shouldn't put business rules in the database. He offered that server-side code can be hard to debug. > > I'm sure many here would love to see such a book published, maybe some talks on the topic given. > > > What might I cover that I haven't mentioned? What are the usual objections to server-side code and how can they be met? When *are* they justified and what should the criteria be to put code in Postgres? Any other thoughts? Any other websites or books on the topic I might consult? Not a specific topic, but as a general theme, a lot of developers don't seem to think it's useful for them to know SQL, and therefore don't bother trying -- or even actively resist learning. So if the overall theme is "knowing this makes things better", I would buy multiple copies of the book an mysteriously leave it on various developer's desks. -- Bill Moran -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
