Set an id on index definitions for use later in the process

3 tests are failing out of my current selections, map reduces are being marked as non-stale when they have not yet finished indexing gosh darnit

Wholly broken code, but you can see where I'm going with this

Compiles apart from the studio, really need to work out where to use ints and where to use strings having now mullered this

Now compiles, and have renamed Name -> Id to make it obvious, nearly to the point of running tests again

Remove compiled generators ala isue #1269

Tests all failing because storage isn't using ids yet, so time to force that

Switched core storage to using ints, now need to spread that among the other core storage classes (mapreduce) and get the tests building again - they use the names to talk to storage and of course, names aren't used in storage any more

Mapped storage converted across to id usage

Converted staleness across to use index ids

Everything apart from studio builds, and most of the storage tests pass, just not the indexing tests

Managed storage doesn't throw a wobbly on integers, but it is expecting strings on read calls

Fixed a couple of snafus, now pondering on why indexes keep coming back as stale - is indexing even taking place I JUST DON'T KNOW

Hacky fix that might not work, silverlight client downloads definitions AND stats and combines the two lists

reduce breaking change by renaming PublicName back to Name now we are using Ids everywhere

Lookup tables for name -> id

Switched to using integer based ids in actual storage

Check for index not existing before deleting

What we need is to rename the column and copy data around, stashing this so I can create a database in the old version to test with

Start by creating the new one then I guess, then we'll rename outside the Tx

Made the bold move of giving the configuration to the updaters because then they can do more things

Some of the Esent stuff written, and the rest of the path is pretty layed out

My cunning plan to delete the old column is for nought, as renaming apparently also updates indexes

Gonna need to do it on a table by table basis, bugger

We need two different strategies - one for where we can do an in-place copy and deal with an auto-increment primary key, and one where we have to copy and re-create the table because we have a natural key

Migration works
Post-merge getting the solution to actually compile
Removed the test for compiled indexes
Removed more compiled indexes tests
Re-implemented code to get index by name
Fixed esent integration for mapped results, int32, not int64...
Merge branch 'RavenDB-1140' of https://github.com/robashton/ravendb into New3

Conflicts:
	Raven.Database/DocumentDatabase.cs
	Raven.Database/Indexing/AbstractIndexingExecuter.cs
	Raven.Database/Queries/SuggestionQueryRunner.cs
	Raven.Database/Queries/TermsQueryRunner.cs
Removing stupid obselete attribute
Making sure we will be using the right index name in index batchers
Removing useless ( and potentially dangerous ) deletion
Making sure that we compare view ids using integers, not strings
Making sure that we send attachment headers
Fixing serialization of Streams
Fixing test
Fixing an issue with auth for bulk insert using windows auth
Fixing tests
Don't use index name fixups, no longer needed
Can handle deletion of non existent index
Restoring explanations feature that got removed in a merge
Fixing tests