I have different entity types in a collection, that is in memory (never saved to disk).

If I define an EntityView of that colleciton and use GetEntityTypeFilter() as the filter, it will NOT return the matching entities.

I ended up just looping through the collection and checking the type of each object.

Please check the following thread: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=12580

That will miss subtypes. If you care about them, you can also use:

[Test]
public void FilterOnTypeInMemoryTest()
{
    using(DataAccessAdapter adapter = new DataAccessAdapter())
    {
        EntityCollection toDelete = new EntityCollection();
        UnitOfWork2 uow = CreateTestBatchForSave2(ref toDelete);
        uow.Commit(adapter, true);

        EntityCollectionNonGeneric employees = new EntityCollectionNonGeneric(new EmployeeEntityFactory());
        adapter.FetchEntityCollection(employees, null);

        //IPredicateExpression filter = ClerkEntity.GetEntityTypeFilter();
        PredicateExpression filter = new PredicateExpression(new DelegatePredicate(
            delegate(IEntityCore toExamine)
            {
                return typeof(ClerkEntity).IsAssignableFrom(toExamine.GetType());
            }));


        List<int> clerksFound = employees.FindMatches(filter);
        Assert.AreEqual(2, clerksFound.Count);

        adapter.DeleteEntityCollection(toDelete);
    }
}

Ok, thanks.

I mainly wanted to post this in case it was a bug. Walla's post said there was going to be something added/changed for this in 2.6?

Not a big deal, because this does not come up for me often, but would be nice if I could just use GetEntityTypeFilter() and not worry about if there are any 'new' entities in my existing collection that would be missed....

We thought of adding it, but the code in my previous post does exactly what you want: filter in memory on a type, so we left it as-is.

GetEntityTypeFilter is indeed for db-filtering.

What about adding a GetEntityTypeFilterInMemory() function?

WayneBrantley wrote:

What about adding a GetEntityTypeFilterInMemory() function?

You don't have to, see my post earlier in the thread with the example how to filter.

Sorry for the confusion, I did see your post earlier.

I just thought it might be clearer if that code you posted above was simply put into a GetEntityTypeFilterInMemory() function on the entity so it would be more 'obvious' and 'easy' for developers to do this kind of filter.

In this case, it's a bit redundant. It would bloat the generated code a bit too much in our opinion, as the creation of the filter is very easy and small.

I just got caught by this same problem. There is no mention in the documentation I have for version 2.6 that GetEntityTypeFilter() does not work for entities in-memory that have not been saved.

I'm happy to work around this as advised in the post above but perhaps it would be worth making a note of this in the documentation (or is mine out of date?).

Thanks for a great product by the way ... turnaround time for developing against our database is sooo fast because of your product. Most importantly, changes to the schema can be accommodated very quickly and safely. Love it!

colincsb wrote:

I just got caught by this same problem. There is no mention in the documentation I have for version 2.6 that GetEntityTypeFilter() does not work for entities in-memory that have not been saved.

I'm happy to work around this as advised in the post above but perhaps it would be worth making a note of this in the documentation (or is mine out of date?).

There's no mention of this in the docs, we'll add such a note, thanks for the suggestion

Thanks for a great product by the way ... turnaround time for developing against our database is sooo fast because of your product. Most importantly, changes to the schema can be accommodated very quickly and safely. Love it!

Thanks for the kind words!