…ent versions, removed jeweler configs and cleaned up gemspec. Author: Nathan <email@example.com> Committer: Nathan <firstname.lastname@example.org>
…metadata entries and aggregation collections not be removed/dropped.
…ain while they ran
*Fixed a bug with the naming of expansion variables when expanding embedded collections or hashes *Refactored the cube processing logic a little to make processing an aggregation somewhat safe even while the aggregation is being queried, by not dropping cached aggregated data but simply overwriting it when map reduce is complete.
*Minor adjustment to prevent Cubicle from vomiting blood and pieces of chewed up cats when filtering a query using MongoDB's new $or operator.
…ion name when possible.
*Added the ability to define aggregations that expand embedded collections, such as hashes or arrays, using the 'expand' expression in the aggregation DSL. Bumping version to 0.5.0 (yes, quite a leap) because this was the last missing piece of functionality before I feel the library is more or less functional for most uses. There is still one more major aspect of Cubicle that needs some work, and that is how dates are handled. Once that is finished, I think it will be ready for 1.0 as it is already in production use in two of our systems and being integrated without troubles into a third.
…tion options, specifically allowing MongoMapper configuration to be supersceded (sp?) [sic]
*Included mustache dependency in gem (whoops) and fixed a bug where an error in cube processing would replace useful error information with nonsensical error information.
*Modified data extraction to ensure that member and query level aliases are respected in the final result. Also stopped automatically dropping temporary map reduce tables during query execution for performance reasons. Instead, added a static method to the Cubicle module, clear_temp_tables, which can be called at application startup or teardown: Cubicle.clear_temp_tables()