Unstored fields not compatible with Views
Aren Cambre - September 11, 2009 - 02:29
| Project: | Computed Field |
| Version: | 6.x-1.0-beta3 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
If the Store using the database settings below checkbox is not selected, then the field is not available to Views. I presume this is because there is no SQL query that Views could use to pull the field?
If this is an unavoidable restriction, the UI needs to make this clear. I recommend explaining this directly in the UI because views is so frequently used.
#1
Marking as feature request since this is not a bug. Views and SQL can only query data is stored in a database. So IMHO this is self-evident.
#2
Seems like this might be a combination of Computed Field, Dynamic Field (see #372314: Merge with Computed Field), and Views Custom Field (see #577012: Merge with Computed Field?).
The goal would be a field that supports dynamic calculation in the view and the node.