Timeline for answer to Why don't relational databases support returning information in a nested format? by Jon Raynor
Current License: CC BY-SA 3.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Jan 9, 2014 at 16:51 | comment | added | Jon Raynor | @SandRock - A database will send back a single result set back from a SQL Query. By identifying levels in the query itself you could create a hierarchical or nested result set that would haev to be processed. I think currently that is closest we are gonig to get to returning data that is nested. | |
| Jan 9, 2014 at 16:48 | history | edited | Jon Raynor | CC BY-SA 3.0 |
added 269 characters in body
|
| Jan 8, 2014 at 23:10 | comment | added | SandRock | I can't find any documentation about sub-resultsets in SQL Server. Even when using a CTE. By resultset I mean rows of data with just enough strongly-typed columns. Can you add references to your answer? | |
| Jul 7, 2011 at 2:59 | history | migrated | from stackoverflow.com (revisions) | ||
| Jul 7, 2011 at 0:18 | history | answered | Jon Raynor | CC BY-SA 3.0 |