i4o - Indexed LINQ

New Post: What is name of dll?

Sanjay_Search — Fri, 28 Dec 2012 08:57:01 GMT

Hi have installed it but I am not able to use

using i4O; which dll reference I have to include where it is located?

Also is there any link where I can find examples on this?

Thanks,

Sanjay

Source code checked in, #69709

Project Collection Service Accounts — Mon, 01 Oct 2012 22:10:56 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69708

Project Collection Service Accounts — Mon, 01 Oct 2012 22:06:45 GMT

Checked in by server upgrade

New Post: Nuget?

mcintyre321 — Tue, 08 Nov 2011 15:41:29 GMT

Whoops sorry for the half written post! I didn't realise I had posted it!

was wondering if there was a Nuget package available? If not I could add one, although it's probably best if the project contributors manage it.

thanks for i4o!

New Post: Double post

mcintyre321 — Tue, 08 Nov 2011 15:38:21 GMT

Ignore this

New Post: Why Github?

ericksoa — Sat, 05 Nov 2011 15:10:03 GMT

Lots of reasons for the move, but mainly to group all my other OSS projects that me or my colleagues maintain together - whether they are .NET or not.

Updated Wiki: Home

ericksoa — Sat, 05 Nov 2011 15:08:56 GMT

Project Description
i4o (index for objects) is the first class library that extends LINQ to allow you to put indexes on your objects. Using i4o, the speed of LINQ operations are often over one thousand times faster than without i4o.

i4o works by allowing the developer to specify an IndexSpecification<T> for any class, and then using the IndexableCollection<T> to implement a collection of that class that will use the index specification, rather than sequential search, when doing LINQ operations that can benefit from indexing.

i4o reduces the amount of code required to implement custom indexes in collections to mere specification of indexes for classes, while allowing LINQ queries over IndexableCollection<T> to automatically use the indexes where appropriate. i4o makes the idea of indexed LINQ not just a theory, but a "here and now" reality.

The latest project update is on Aaron's Blog at http://nomadic-developer.com/2010/03/02/i4o-v2/

The link below will describe different ways you can setup the IndexableCollection<T>'s indexes.
http://staxmanade.blogspot.com/2008/12/i4o-indexspecification-for.html

The source for this is now being maintained on github https://github.com/ericksoa/i4o

Updated Wiki: Home

ericksoa — Sat, 05 Nov 2011 15:08:30 GMT

New Post: Nuget?

ericksoa — Sat, 05 Nov 2011 15:07:49 GMT

We moved the project over to github a few months ago: https://github.com/ericksoa/i4o - sorry for any confusion.

New Post: Nuget?

mcintyre321 — Fri, 04 Nov 2011 10:38:56 GMT

It looks like the TeamCity build is failing, so I guess the latest code is not the right thing to

New Post: Why Github?

bherila — Wed, 27 Apr 2011 02:01:26 GMT

Out of curiosity, why did you decide to move the source from TFS to Git?

Commented Issue: Using Union and Intersect in WhereThroughIndex in i4o v2 [19925]

Gregory1981 — Tue, 15 Feb 2011 16:47:21 GMT

In v2 branch in WhereThroughIndex results from different indexes are combined using Union and Intersect. However Union and Intersect, while operating on IEnumerable interface, are set operations. They return sets, and because of that they remove duplicates. So, there's a bug: if original sequence contains duplicates, result returned from WhereThroughIndex with complex query is not.
Comments: ** Comment from web user: Gregory1981 **

The issue is that WhereThroughIndex sometimes returns duplicates and sometimes not, which is inconsistent and confusing.
Here it is:

[Test]
public void SuperComplexQueryWithDuplicates()
{

var single = new SimpleClass { Name = "Jason Jarett", Age = 25, FavoriteColor = Color.Aqua };
SimpleClass[] someItems = {
single,
single,
single,
single
};
var indexSpec = IndexSpecification<SimpleClass>.Build()
.With(person => person.FavoriteColor)
.And(person => person.Age)
.And(person => person.Name);
var theIndexSet = new IndexSet<SimpleClass>(someItems, indexSpec);
var result =
from item in theIndexSet
where item.Name == "Jason Jarett" && item.Age == 25 && item.FavoriteColor == Color.Aqua
select item;
Assert.AreEqual(4, result.Count());
}

Commented Issue: Using Union and Intersect in WhereThroughIndex in i4o v2 [19925]

staxmanade — Tue, 15 Feb 2011 05:24:12 GMT

I'm struggling to see what your issues is. Any you can produce a test?

Source code checked in, #58067

staxmanade — Mon, 14 Feb 2011 23:05:51 GMT

Moved source over to github - https://github.com/ericksoa/i4o

New Post: Status of v1.0 with advanced Where that takes advantage of multiple indexed properies

staxmanade — Mon, 14 Feb 2011 22:48:40 GMT

Ok - major updates have been pushed - full silverlight and .net fwk support is now in there.

If it's missing a feature you need - feel free to fork now and hack away.

Looking forward to any pull requests & happy coding.

New Post: Status of v1.0 with advanced Where that takes advantage of multiple indexed properies

staxmanade — Mon, 14 Feb 2011 22:14:12 GMT

Actually looks like I've already done a bunch of the Silverlight work - just doing a little cleanup now and will have the changes pushed up to github master.

New Post: Status of v1.0 with advanced Where that takes advantage of multiple indexed properies

staxmanade — Mon, 14 Feb 2011 20:23:09 GMT

We know the updates to i4o have been a long time coming. (That's the problem w/ open source and real life eh?)

Currently we've moved the v2 code over to https://github.com/ericksoa/i4o

Feel free to fork and send a pull request if you have updates to make. Or if you'd like to discuss anything go ahead and start a new discussion thread.

Currently on the TODO list is to bring back possible silverlight support - the code here https://github.com/ericksoa/i4o has taken a dependency on some code that in't supported in silverlight - so it's be nice to clean that up if possible.

Thoughts?

New Post: Status of v1.0 with advanced Where that takes advantage of multiple indexed properies

shatl — Mon, 14 Feb 2011 17:21:16 GMT

Hi,

any updates regarding v2?

It looks very promising, please let mw know if I can help you with development..

Created Issue: Using Union and Intersect in WhereThroughIndex in i4o v2 [19925]

Gregory1981 — Sun, 06 Feb 2011 14:46:46 GMT

In v2 branch WhereThroughIndex results from different indexes are combined with Union and Intersect. However Union and Intersect, while operating on IEnumerable interface, are set operations. They return sets, and because of that they remove duplicates. So, there's a bug: if original sequence contains duplicates, result returned from WhereThroughIndex with complex query is not.

Source code checked in, #56713

staxmanade — Sun, 02 Jan 2011 00:56:44 GMT

Renamed file. Removed un-used property PropertyName on IIndex<T> Added the PropertyReader class in to replace the reflection reading Replaced .ToList.Each() with a custom extension .Each() to reduce needed list creations