v0.3.45

Fixes

• Reference name collision (#158, thanks @vadim-dedkov): relation names are not globally unique — the default <target>_<field> of an incoming FK can equal the name of an unrelated M2M projection. Navigation fields now resolve their relation by name, target, field and junction, so a reverse FK no longer resolves to an M2M projection (and vice versa).
• M2M relation aggregations (#159): <m2m>_aggregation / <m2m>_bucket_aggregation on an M2M endpoint now join the junction table. Previously they compiled an invalid root condition. Also:
  • junction keys are referenced by their columns (@field_source renames);
  • DuckDB sources keep the junction's catalog prefix;
  • a junction carrying a reference beyond its two legs resolves the correct leg (select, filter, insert, aggregation).