- Joins that know about the foreign keys already declared in the table definitions. - Structured rows to kill all grouping special cases and the distinction be

- Joins that know about the foreign keys already declared in the table definitions. - Structured rows to kill all grouping special cases and the distinction between where and having. - Hierarchical rows so that join(Planet, Person) doesn't repeat Planet columns in each returned row. Linq already gets you 1 and 2. See http://www.linqpad.net/WhyLINQBeatsSQL.aspx http://www.linqpad.net/WhyLINQBeatsSQL.aspx Xml gets you 3.