Excuses, excuses, excuses... Login and vote now.
By bloid
via weblogs.sqlteam.com
Published: May 02 2007 / 13:44
As I read somewhere once, you don't tell SQL how to do it, you tell SQL what you want, and that's a great way of thinking about it. A procedural programmer gets bogged down with the details, and has to concentrate on breaking things down into small pieces, explicitly reading and processing one row of data at a time, and figuring out how to combine those results together at the end to make it all work. A set-based SQL programmer worries about none of those things: In the set-based world, you state your relations and join the tables together, add some grouping and criteria, and it is the database engine that worries about the specifics.
-
Startups pass on Silicon Valley to find their fortunes in New York
-
Cross page posting Submit Form Server.Transfer methods ASP.NET
-
Attila Szegedi on JVM and GC Performance Tuning at Twitter
-
Spring and Scala talk: slides, video and source code
-
Principles of an Indie Game Bottom Feeder
-
there's a major security flaw in Android design
Add your comment
