Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.i had a thought how to make apachesolr_views a little bit more flexible.
What about just get the nids from apachesolr and so an easy select FROM WHERE nid IN ().
This query is runned in something like pre_render but once for the whole solr-query. With this it could be possible to have every module which is integrated into views availible for apachesolr-listings.
So there would be one additional query, but quite a lot of flexibility. Any ideas?
Comments
Comment #1
Scott Reynolds commentedYa so this is what I have been talking to people about #621818: Possibility to add relationship to nodes. Its been planned for awhile just haven't gotten around to it. The basic idea is to have the Solr Query object have several views_query_default object in it to handle the different base tables (Soon Solr will have user searching thats why an array() is important here).
So the existing standard sql handlers can do ensure_my_table() and have that work. Luckily, almost all of the standard views_query_default methods haven't been implemented by the Solr Query object. So we already have things properly namespaced. (things like add_where, add_field, ensure_table) so I feel pretty confident that will work.
If that makes sense to ya sweet :-D. Its something Im dieing to get implemented and I am pretty sure it can be implemented.
Comment #2
dawehnerIts cool, that this makes sense for other people too :)
Thats exact as i thought about it.
Why not support any kinds of views query objects, for example http://drupal.org/project/xdb
Views allows so much more here.
Comment #3
Remon commentedany news about this? :)
Comment #4
Scott Reynolds commentedGood news, I wrote a patch for this here: #576286: Add general SQL support. It needs small touch ups but its a big start and I want it in.