lazy fields are always lazy.....

BIZ TMS XData
1

a TXDATAClient is created as follows:

localc:=TXDataClient.Create; 
localc.Uri:='http://127.0.0.1:1234/path/v1/';
localserv:=localc.Service<IlocalServices>;
localc.HttpClient.OnSendingRequest:=procedure(Req: THttpRequest) 
begin 
Req.Headers.SetValue('xdata-expand-level','1'); 
end;

The following XData service interface implementation has a Tblob dat field in a class where dat is NOT declared as lazy:
result:=obj.Find<tapistorage>.Where(Linq['typid']._In(a)).CreateAlias('dat','hadenough',TFetchMode.Eager).List;
But the dat is still by reference in the response.

How can I DISABLE this lazy things?
I am starting to believe to no-lazy ORMs......

2

How do I add the expand when calling a function from the interface Serviceimpementation?
Just to notice also that Tapistorage is removed as Aurelius CRUD from the Xdata Aurelius model, so I can not request a Tblob by implementation..... but Aurelius can not understand that......

Unknown path "(1)/dat"
is the lazy Aurelius error message

3

I replaced the Tblob with Tarray<byte> and now the field is returned.
What other possibilities I have except Tarray<byte>?
Tarray<byte> fields can not be resized with setlength and it is memory consuming.

Of course the bug "Unknown path" still needs a fix