I've been building efq_views support for http://drupal.org/project/fluxservice - such that you can use efq views to list tweets without storing them in the database at all. We've got remote entities implemented there, thus we have no local schema or database associated.

When using efq_views with that I ran over the problem that efq_views assumes a schema and thus triggeres some notices on cache clear. Attached patch addresses that by respecting the entity API's property info key for "queryable" which is here for telling us whether something is queryable via EFQ.

We miss a separation for filtering and sorts in the metadata, so I think it's best to just assume that we have both when something is queryable. efq_views did check for a base-table schema field previously, but that's not really a requirement for an efq property to be sortable as a) there might be no schema at all and b) it might be a schema field in a non-base table.

CommentFileSizeAuthor
d7_efq_views_remote.patch1.26 KBfago
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

chx’s picture

Status: Needs review » Fixed

Committed, thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.