"Compounded Filter" - create filter for filtering several concatenated fields which

The patch was developed against 7.x-3.x, there is nothing which can be changed here.

A backport should be actually much less code.

This time with proper seperation of the spaces.

Here is a version with a multi-select as ui.

Thanks for providing the patch - unfortunatly it causes in SQL error while using Field-API Fields. If you look in the SQL-Query the table names are missing for the fields. In my case i'm using domain_access - but this should not crash the query - non-filtered output is ok.

SELECT DISTINCT users.uid AS uid, users.name AS users_name, 'user' AS field_data_field_user_vorname_user_entity_type, 'user' AS field_data_field_user_name_user_entity_type
FROM 
{users} users
LEFT JOIN {domain_editor} domain_editor ON users.uid = domain_editor.uid
LEFT JOIN {domain} domain_domain_editor ON domain_editor.domain_id = domain_domain_editor.domain_id
LEFT JOIN {domain_access} domain_domain_editor__domain_access ON domain_domain_editor.domain_id = domain_domain_editor__domain_access.gid AND domain_domain_editor__domain_access.realm = 'domain_id'
WHERE (( (domain_domain_editor__domain_access.gid = '1') AND (domain_domain_editor__domain_access.realm = 'domain_id') ) AND(( (CONCAT(.field_user_vorname_value) LIKE 'Steffen'))))

SteffenR

Hey that's not an already existing bug :)

Here is a small improvement to the patch, which simply requires to add the table to the query all the time.

@dereine - thx for rerolling the patch - i tried it on my view and it worked like charme. It would be great if we could bring it into views core..

SteffenR

Thanks for the testing!

Committed with some small improvements, see patch to 7.x-3.x

Now the patch can be backported to 6.x-3.x

Sorry, Daniel, I have to reopen this issue for D7 again, as there is a problem with relationships, due to the $field->ensure_my_table(); part in pre_query(). It breaks the relationships, as $this->_pre_query(); is called before $this->_build('relationship'); in view::build().

One thought to fix this, could be moving ensure_my_table() to query(). I'll test this with SteffenR's help.

Like derhasi said, we retested the whole thing by putting ensure_my_table directly into the query() - function.
In my testings it worked fine - i hope it won't break any other "views - query - building - stuff" ..

Attached you find a patch that should apply to the latest views DEV ..

I tested it on the view that created the problem, and I've to say, it works with the additional patch of #13 (plus #10).

-    // Always add the table of the selected fields to be sure a table alias exists.

You asked for a review here is one. It would be cool to still have this comment

dereine, ok, there's the comment ;)

Thanks! Now let's backport it. For other patches it might be helpful to create new issues, so it's less confusing.

Okay here is a patch for the port.

I've only tested it on one view in D6, but it worked. Excellent functionality.

Am I understanding I might be able to type data into one filter but include other fields to be searched upon? I'd really enjoy this. If so, is there a patch or module for Views 7.3?

+++ b/handlers/views_handler_filter_combine.incundefined
@@ -0,0 +1,79 @@
+//      $field->ensure_my_table();

"Awesome"

+++ b/handlers/views_handler_filter_combine.incundefined
@@ -0,0 +1,79 @@
+      if (!empty($field->field_alias) && !empty($field->field_alias)) {

This line should really check for both table alias and field alias.

I mean exactly that line. It should be more like if (!empty($field->table_alias) && !empty($field->field_alias)) {