Conflicts: _layouts/default.html community.markdown content/articles/datamapper_090_released.markdown content/articles/spotlight_on_cpk.markdown content/articles/stunningly_easy_way_to_live_on_the_edge.markdown content/articles/the_great_refactoring.markdown content/development/index.markdown content/docs/associations.markdown content/docs/create_and_destroy.markdown content/docs/dm_more/types.markdown content/docs/find.markdown content/docs/index.markdown content/docs/install.markdown content/docs/misc.markdown content/docs/validations.markdown content/getting-started.markdown content/why.markdown index.markdown Signed-off-by: Alex Coles <firstname.lastname@example.org>
Previously this was buried in the old contribution guide only.
We now only mention that property and relationship *names* are available as keys in nested conditions. While it's technically possible to use Property objects as keys too, I'd think that the use for that is maybe rather rare. We can always add it later if we decide that it's worth going into that much detail. Using relationship objects as keys was confusing and wrong to begin with. A future commit will add some docs for constructing QueryPath objects, which is the actual concept behind the idea.