Posted by Aren Cambre on September 11, 2009 at 2:29am
Jump to:
| Project: | Computed Field |
| Version: | 6.x-1.0-beta3 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
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.
Comments
#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.
#3
php can carry out computations not just sql...
In Views template files I am storing computations which access data provided to views but not displayed...
#4
#343786: Views 2 Integration
#5
I'm not seeing the issue duplication.
#6
"The goal would be a field that supports dynamic calculation in the view and the node."
Well as long as you aren't trying to filter or sort on this "dynamic calculation" then you can just get creative and put your logic in the computed field "display code" which is always run before the field is displayed. However, if you are trying to filter or sort on this output then it would have to be in the db for Views to work with via SQL. Closing issue as really non-sql field support in Views is sort of an oxymoron.
#7
With Views Styles we will have the ability to use jquery grids and tables which can do client side sorting, like http://www.drupal.org/project/datatables, so it may work sometime in the future :)