Class SqlPathContext<S,​Q extends FlexibleRelationalPathBase<R>,​R>

  • Type Parameters:
    S - schema type, used by encapsulated mapping
    Q - type of entity path
    R - row type related to the SqlPathContext
    Direct Known Subclasses:
    SqlQueryContext

    public abstract class SqlPathContext<S,​Q extends FlexibleRelationalPathBase<R>,​R>
    extends Object
    SQL path context with mapping information.

    TODO if this proves to have a single subclass in, say, 2022, merge them into one, please The idea is/was that not every context requires query - or represents the whole query. Some sub-contexts may create inner query, e.g. in EXISTS clause. On the other hand, even if sub-context does not represent the new query but only part of existing one, e.g. JOIN path, we still need access to the original query, for instance to add another JOIN, or test existing joins, etc. But this can be done by creating new SqlQueryContext with the same query and different path. So - if no special needs arise (e.g. for EXISTS support)... merge these classes. ;-)