Hi everyone,

Sorry, another question for you! I'm using the following code to create a set of projectors so I can project onto an entity collection, as I need to have a groupby/having clause - even though the resultset itself is just the entity fields:

List<IDataValueProjector> valueProjectors = new List<IDataValueProjector>(entityFields.Count); foreach (EntityField2 entityField in entityFields) { valueProjectors.Add(new DataValueProjector(entityField.Alias, entityField.FieldIndex, entityField.DataType)); } DataProjectorToIEntityCollection2 projector = new DataProjectorToIEntityCollection2(entityCollection);

da.FetchProjection(valueProjectors, projector, entityFields, relations, 0, null, groupByClause, true, 1, 10);

which works great. Except when one of the columns in the entity is an integer column set up to automatically convert to an enum. Is there any way to do this, without getting in to a whole load of special cases building up a projection that ideally I shouldn't be having to build in the first place?

Cheers

Projections don't use type converters themselves. If you want to, you have to create a derived class of the datavalueprojector class.

Frans - is there any way at all that we could have a parameter for FetchEntityCollection with a groupBy clause? The lack of one is the only reason I'm having to use a projection, and I'm loathed to have to go and implement further special cases that might bite me again later if I can avoid it?

Would appreciate your thoughts on this!

It's not logical to have a groupby clause. The thing is: an entity is represented by a table row/view row in one or more tables/views. A query result of a groupby is a new set, it's not a set in a table/view, so you then actually are mapping your entity onto a set resulted from a group by instead of a table/view.

In v2.6, we'll introduce derived tables, (select * from (select * from ... )), which would allow you to create a set with groupby and use that as the source for an entity fetch.

Ah, thanks Frans - it's the derived table scenario that I need here!

Otis wrote:

In v2.6, we'll introduce derived tables, (select * from (select * from ... )), which would allow you to create a set with groupby and use that as the source for an entity fetch.

Fantastic!

Cheeky question - when is 2.6 due out?

Continuing to be impressed by LLBLGen... and the quality of the support. Keep it up guys!

james.crowley wrote:

Cheeky question - when is 2.6 due out?

Aren't you the one doing stand-up comedy on friday nights? . When it's released, I have no idea, but it won't take 9 months like 2.5 did I'm currently busy designing the derived table stuff, I hope to have something working by the end of the day. After that, Linq support is going to be more straight forward. (I hope ). We're only planning to add Linq support, some Api changes for bugfixes and stuff supporting Linq and that's it. So no other features will be added.

Continuing to be impressed by LLBLGen... and the quality of the support. Keep it up guys!

Thanks!