start for finding with $near
adding command geoNear
distanceSpherical is good
Merge branch 'idfirst' into geonear

Conflicts:
	src/main/java/com/foursquare/fongo/impl/Util.java
	src/main/java/com/foursquare/fongo/impl/index/IndexAbstract.java
	src/test/java/com/foursquare/fongo/FongoIndexTest.java
	src/test/java/com/foursquare/fongo/FongoTest.java
respect insert order in GeoIndex
Merge remote-tracking branch 'github/master' into geonear
trying geoIndex more
Merge branch 'correct_inner_index' into geonear

Conflicts:
	src/main/java/com/foursquare/fongo/impl/index/IndexAbstract.java
	src/test/java/com/foursquare/fongo/FongoIndexTest.java
more real perf test
remove synchronized because the synchro is done by FongoDBCollection (for update in example, synchronized must be done on FongoDBCollection, not IndexAbstract
change LatLong with your own
commit resolution for index2d
log --
lng/lat
handle DBOject as stored value for $near
Merge branch 'master' into geonear

Conflicts:
	src/main/java/com/foursquare/fongo/impl/index/IndexAbstract.java
	src/main/java/com/mongodb/FongoDB.java
	src/test/java/com/foursquare/fongo/ExpectedMongoException.java
	src/test/java/com/foursquare/fongo/FongoIndexTest.java
	src/test/scala/com/foursquare/fongo/FongoAggregationScalaTest.scala
with latest version of rhino
clean up
Multiple projection with same prefix: last projection is the only that survives

When asking multiples projections that had the same prefixes
(eg: "a.b.c", "a.b.d") only the last projection survive.
This is not the expected behaviour in mongo.

The solution is try to reuse the the result values.
Work with projection with boolean value.

Before this change only numeric projections ({foo: 1} were accepted, while
boolean projection are valid ({foo: true}.

In particular Morphia (https://code.google.com/p/morphia/)
Query#retrievedFields creates a projection using booleans.