I believe this needs to wait for the type system and SQL-gen changes we are working on for 6.0. The type system, as currently designed, tries to handle the composite values the same as any other value. So, for example, you could make the entire composite/embedded on a entity lazy and it would work; however lazy within those will not work. The other piece is the SQL generation. That could possibly re-work that to support this within 5.x, but the SQL generation code is very difficult to introduce changes to (VERY brittle) which is actually the main impetus for 6.0 - the type changes are just a pre-requisite part of that. The current type system is very bad in terms of modeling metadata regarding a composite/embeddable at any level. Or I should say that the type system, as currently designed, |