If I understand it correctly, for a query with joins, then instead of returning a single combined set of results with the information you need, it returns multiple sets of results based on each separate table.
But I don't understand why that would ever be desirable.
I always write my queries to return the information I need, per whatever "key" I need, in each row. Splitting that up in multiple sets of results is not helpful.
Or if I really need multiple sets of data, I write multiple queries.
So I really don't get what this is for. It's like it takes one of the biggest features of databases -- joins -- and removes it? Why?
If I understand it correctly, for a query with joins, then instead of returning a single combined set of results with the information you need, it returns multiple sets of results based on each separate table.
But I don't understand why that would ever be desirable.
I always write my queries to return the information I need, per whatever "key" I need, in each row. Splitting that up in multiple sets of results is not helpful.
Or if I really need multiple sets of data, I write multiple queries.
So I really don't get what this is for. It's like it takes one of the biggest features of databases -- joins -- and removes it? Why?