Using $or filters nullifies columns and produces an exception due to an invalid SQL query

[f-liva]

The filtering of a relationship, when included in an $or clause as shown in https://abbasudo.github.io/laravel-purity/advanced/param.html#changing-params-source, causes the following kind of error:

Query: /users/?filters[$or][profile][name][$contains]=John

SQLSTATE[42S22]: Column not found: 1054 Unknown column '' in 'WHERE' (Connection: mariadb, SQL: select count(*) as aggregate from `users` where ((`` LIKE %John%)))

The raw query produced by Purity becomes:

select * from `users\` where \`\` LIKE '%John%'

Whereas the same query without the OR works correctly: /users/?filters[profile][name][$contains]=John

And produces a correct query:

select * from `users` where exists (select * from `profiles` where `users`.`id_profile` = `profiles`.`id` and `name` LIKE '%John%')

Note

The problem also occurs when using $or with conditions on NON-related columns.

Example: /users/?filters[$or][email][$contains]=@gmail&filters[$or][created_ate][$contains]=2025

Produces:

SQLSTATE[42S22]: Column not found: 1054 Unknown column '' in 'WHERE' (Connection: mariadb, SQL: select count(* ) as aggregate from `users` where ((`` LIKE %@gmail@%) or (`` LIKE %2025%)))

[f-liva]

For example, if I add this test to tests/Feature/FilterableTest.php it fails:

public function it_can_filter_relations_with_or_operator(): void
    {
        $post = Post::create(['title' => 'laravel purity']);
        $comment1 = Comment::create(['content' => 'the quick brown fox jumps over the lazy dog']);
        $comment2 = Comment::create(['content' => 'how quickly daft jumping zebras vex?']);

        $response = $this->getJson(
            '/posts?filters[$or][0][comments][content][$contains]=fox&filters[$or][1][comments][content][$contains]=zebra'
        )
            ->assertOk()
            ->assertJsonCount(2);
    }