Skip to content

subqueries: allow reference to master attribute with mapping; throw on unsafe {master}.attr (not wrapped in [{master}.attr] or attr not exists in master)

Pavlo Mashliakovskiy requested to merge fix/correlationWithMappedAttr into master
  • subqueries: allow reference to master attribute with mapping, for example, [{master}.dfxDocID] in case dfxDocID in mapped to another field. Before this fix such expression put into resulting SQL an attribute name instead of field name attribute is mapped to
  • BREAKING in case of unsafe (not bracket in []) expression for correlation, like [sourceID]={master}.ID server now raise an exception. Valid expression in this case is [sourceID]=[{master}.ID]. Should not affect most of the applications, may be some very old code with manually created UBQLs.
  • UBQL expression for extracting attribute of type many now uses safe [sourceID]=[{master}.ID] instead of unsafe [sourceID]={master}.ID
  • speed-up SQL builder for mapped attributes by pre-calculating mapped expression for current database dialect during domain loading

Merge request reports