Download & Extend
Issues

[META] (Re)introduce Views data integration for core modules

Comments

#1

Posted by xjm on November 29, 2012 at 12:35pm
Title:[META] Reintroduce Views data integration for core modules» [META] (Re)introduce Views data integration for core modules

#2

Posted by xjm on November 29, 2012 at 12:35pm

dblog has also come up several times, so we might want to add integration for that as well.

#3

Posted by pounard on November 29, 2012 at 12:43pm

Watchdog is pluggable and this integration would work only with the dblog module, which may end up being useless for a lot of big-sized sites which will prefer either disabling it, either using a more performant or custom logging solution.

#4

Posted by catch on November 29, 2012 at 1:06pm

At #3, that doesn't stop the dblog module providing its own views integration, if you switch off dblog module then the views integration goes with it.

Where it does get trickier is with #1289536: Add test coverage and/or one real use of PSR-3 based watchdog logger object or any other system where hook_watchdog() moves to a pluggable class.

#5

Posted by dawehner on November 29, 2012 at 2:16pm

If someone wants to implement dblog views integration, please try to do something else.
I have a bunch of people which could help with that and maybe the other views integration issues.

#6

Posted by xjm on December 15, 2012 at 11:09pm

We noticed today that Forum has a denormalized {forum_index} table, and it could make sense to introduce integration for that table rather than joining across to Node and Taxonomy and so on.

Out of scope, but I have the vague notion that core could use some generalized solution for these index tables, for query abstraction and so on.

#7

Posted by catch on December 17, 2012 at 11:26am

@xjm the generalized abstraction is http://drupal.org/project/mv it's been around for years and no-one's ever tried to get it into core (or even a stable contrib release), it is needed though yes.

#8

Posted by klonos on April 20, 2013 at 2:06am

I was pointed to this issue from #1972282: 'Missing handler: node created_year_month argument', but this is a META with a lot of children issues. I have no way to tell which commit from the issues mentioned in the summary could have caused it (if it actually did) and it might be a duplicate of another issue already filed.

Does anyone have a clue?