Kimbo's answer is correct.
I try to explain this to people in several ways. But basically, the table itself is a design similar to a view. Unlike traditional databases, the table itself is not saved to disk and then indexed differently. Projections handle sorting, indexing, disk layout, etc.
I also use the deck of cards analogy. A table can be considered a deck of cards. You ask for special hands. Projection is like random shuffling. Some may be sorted by costume. Some at par. And depending on what you ask, it depends on what projection (in this similar shuffle) you request.
geoffrobinson
source share