In the case where a schema definition contains multiple embedded record expansions pointing to the same table, but where each expansion exposes different fields to return, it is undefined which field set will be associated with each expanded field.
In the above case, it is undefined whether expand1 and expand2 will contain a record with the fields name and enabled; or fields name, email, and password. The values are seen to switch intermittently.
This is almost certainly a cache optimization gone wrong (e.g.: keying on just identity instead of indentity+fields).
In the case where a schema definition contains multiple embedded record expansions pointing to the same table, but where each expansion exposes different fields to return, it is undefined which field set will be associated with each expanded field.
e.g.:
In the above case, it is undefined whether
expand1
andexpand2
will contain a record with the fieldsname
andenabled
; or fieldsname
,email
, andpassword
. The values are seen to switch intermittently.This is almost certainly a cache optimization gone wrong (e.g.: keying on just identity instead of indentity+fields).