if ( !inSelect && queryableCollection != null && CollectionProperties.isCollectionProperty( path ) ) {
	// If this from element is a collection and the path is a collection property (maxIndex, etc.)
	// requiring a sub-query then generate a sub-query.
	//h
	// Unless we are in the select clause, because some dialects do not support
	// Note however, that some dialects do not  However, in the case of this being a collection property reference being in the select, not generating the subquery
	// will not generally work.  The specific cases I am thinking about are the minIndex, maxIndex
	// (most likely minElement, maxElement as well) cases.
	//	todo : if ^^ is the case we should thrown an exception here rather than waiting for the sql error
	//		if the dialect supports select-clause subqueries we could go ahead and generate the subquery also

	// we also need to account for cases where the property name is a CollectionProperty, but
	// is also a property on the element-entity.  This is handled inside `#getPropertyMapping`
	// already; here just check for propertyMapping being the same as the entity persister.  Yes
	// this is hacky, but really this is difficult to handle given the current codebase.
	if ( persister != propertyMapping ) {
		// we want the subquery...
		DeprecationLogger.DEPRECATION_LOGGER.logDeprecationOfCollectionPropertiesInHql( path, fromElement.getClassAlias() );
		return getCollectionPropertyReference( path ).toColumns( tableAlias );
	}
}