Want to give you a heads up that I'm working on a combo field storage engine that utilizes much of the work being done here: http://drupal.org/sandbox/phayes/1635774 . This module stores fields *both* in MySQL *and* in MongDB. When loading entities, or querying them using EntityFieldQuery, it uses MongoDB. When using views, it uses MySQL. Have your cake and eat it too!

Comments

phayes’s picture

phayes CreditAttribution: phayes commented

Would you be interested in housing this module within the mongoDB project?

chx’s picture

chx CreditAttribution: chx commented
Status: Active » Closed (won't fix)

All the efforts are going the opposite direction: make Drupal need less SQL. Adding more data to MySQL is counterproductive. In fact I am considering doing adding an option to remove the last vestiges of the entity data in MySQL (using the same prefix trickery as revision-fu does). Querying MySQL defeats the whole purpose of having your data in MongoDB, namely having fast queries. I am not interested in this , sorry.

phayes’s picture

phayes CreditAttribution: phayes commented

I've gone ahead and created this project here: http://drupal.org/project/combo_field_storage

I know you don't agree with it as a long-term solution, but it fulfills a useful niche.

phayes’s picture

phayes CreditAttribution: phayes commented
Issue summary: View changes

updaing sec