Simple stuff
Joined: 09-Nov-2006
Hi,
I love your product. The only thing that bugs me is that VERY simple things get VERY difficult 
But we knew that.
When i make a FetchEntity call, how can I restrict which fields actually get loaded? In plain SQL i would just remove the field form the select query. I can't seem to find the solution to this very simple problem. I have a blob field that I want to exclude from the normal fetching of the entity and only load that explicitly when i need it.
Please enlighten me 
Best regards Frederic Gos
Joined: 09-Nov-2006
Otis wrote:
That's a feature we've planned for v2.1, the free upgrade for v2.0, which is currently in development.
At the moment, the only way to overcome this problem is by fetching a projection and omitting the blob field and projecting the result onto the entity type.
Ah ok, thx.
I dug a bit further and looked at the Entity code. Wouldnt it be possible to derive
a new Factory class from the existing factory, fildle with the fields and hook up that new factory into the thing to achieve what i want? Would that not remove the blob field form the underlying query? Just want to check if im thinking straight here
anyways, thx Otis
Fritzoid wrote:
Otis wrote:
That's a feature we've planned for v2.1, the free upgrade for v2.0, which is currently in development.
At the moment, the only way to overcome this problem is by fetching a projection and omitting the blob field and projecting the result onto the entity type.
Ah ok, thx.
I dug a bit further and looked at the Entity code. Wouldnt it be possible to derive a new Factory class from the existing factory, fildle with the fields and hook up that new factory into the thing to achieve what i want? Would that not remove the blob field form the underlying query? Just want to check if im thinking straight here
anyways, thx Otis
Yes that would work