Top Ten Reasons to use EntityFieldQuery (EFQ)

Drupal 7 introduced a great class, EntityFieldQuery (EFQ), to easily grab information from entities that was not available in Drupal 6.

This session will explore why you should be already using EFQ in your development practices. We'll also review how to use it and explore it's relationship with Drupal view modes and block entities (Beans).

This session will also explore comparisons with Views, and how EFQ should replace some of the common development practices using Views as a query tool.

EFQ Top Ten

  1. Core
  2. Well Documented
  3. Simple
  4. Consumable
  5. Object-Oriented
  6. Extensible
  7. Alterable
  8. Exception Handling
  9. View Modes
  10. Beans
Track: 
Coding and Development
Experience level: 
Intermediate

Comments

This sounds like an interesting session. I am definitely interested in comparisons with Views. Will you include performance in that comparison?