I'll save ppl some time: * first 20 mins: Writing a contrived report query that's easy in SQL is easy in SQL. * but: most real reports require many different

I'll save ppl some time: * first 20 mins: Writing a contrived report query that's easy in SQL is easy in SQL. * but: most real reports require many different fields collated into many parts of say a pdf or xls. Once you take this into account writing custom code to do the entire report is often the only way to do it. :< * you often can't do some of what the author suggests bc in a "real" org you have db zealots that only allow access to their precious through stored procs and a surprisingly large number of meetings * trying to do some non-trivial where clauses? Not in SQL - so you have to use an external lang. I call this "Works in my presentation" syndrome. * he acts surprised that a lang that uses a db through a SQL api can't be as fast/efficient/terse as a system that uses SQL and has direct access to the db/storage. Stopped after that. PS Seems like a funny guy tho - liked his style! :>