is_cross_db is now a function not a property anymore (for having not implemented errors and a default definition)
embed_through now also affects the query base. For backward compatibility an empty string restores the old behaviour (default)
there is a slightly difference: when traversing m2m forward it returns the through model, so both sides are symmetrical
this is also for matching the querying syntax of the field
m2m fields are now full proxying between start and end side
embed_parent/embed_through can be queried like a field when specified
add tests for the fallback behavior and for embed_through in use
fix distinct. Neither the function would issue an distinct without arguments, nor the m2m would work with newer versions where a compile error would be issued when columns were specified on non-postgresql dbs.
docs are updated and if embed_through is not used, everything works backward compatible.
Changes:
docs are updated and if embed_through is not used, everything works backward compatible.
Note: there should be some tests for embed_parent