It could be possible to accomplish - and indeed has been done - by setting up a single MyISAM table that basically cross-references other tables during cron and stores the primary key along with data. I'm not sure it about it because of the obvious drawbacks of storing duplicate data in the database, but I would certainly like to play with the idea, do some test, and see how it works out. It would clearly be beneficial to support INNODB and not have to force users to allow the change, but FULLTEXT searches require MyISAM and that's how the module will always determine relevancy.

Currently I'm working on Rules forms support to get some new features into that module, but this is definitely an idea worth looking into and I'll gladly do so when we're more caught up on that module (probably this weekend). If anyone wants to provide a patch for this in the meantime I'll gladly review and commit a stable patch.

Comments

jordojuice’s picture

jordojuice CreditAttribution: jordojuice commented
Version: 7.x-2.x-dev » master

Err... This would go in both versions actually.

Juan C’s picture

Juan C CreditAttribution: Juan C commented

Subscribe

franzkewd’s picture

franzkewd CreditAttribution: franzkewd commented

+1

opdavies’s picture

opdavies
He/him
Primary language English
Location Wales
CreditAttribution: opdavies commented

+1

jordojuice’s picture

jordojuice CreditAttribution: jordojuice commented

Alright, since I've put a lot of work into fixing the bugs and adding features after the release of Views 3, I think this is a good core issue to get back into. Note: while I've read that it can be done, depending on how it affects queries there may need to be an option for this on a module settings page. Another note: since working with the Views integration and trying to support extra fields, with the way the fields are stored in the database - all on different tables and thus indexed separately - it could even mean a performance improvement to have data in a single table. As of now, with indexes on several different tables, in some cases multiple MATCH expressions have to be used in the same query, and that's not too efficient.

I'm open to patches for this on any version. Otherwise I think I'll be looking at it again because it is a nice challenge.

itz_andr3’s picture

itz_andr3 CreditAttribution: itz_andr3 commented

+1