Hello,

I have an issue : In the example below there is 100 Project and 0 Formation in DB, so /testA and /testB should return the exact same thing :

    Route::get('/testA', function (Request $request) {
        return Search::addMany([
            [Project::query(), 'title'],
        ])->get('');
    });

    Route::get('/testB', function (Request $request) {
        return Search::addMany([
            [Project::query(), 'title'],
            [Formation::query(), 'title'],
        ])->get('');
    });

But it is not the case, I don't get the results in the same order in the 2 queries, event if I add ->orderByRelevance()

Any idea why is this ? Thank you

Hi,

Is there any way to order by relationship count ?

$query = User::withCount('posts');

Search::new()
    ->add($query, 'email', 'posts_count')
    ->get();

If I try this, I get this error:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'users.posts_count' in 'field list' (SQL: select users.id as 0_user_key, users.posts_count as 0_user_order from users order by COALESCE(0_user_order) asc)

I guess I have to replace the eager loaded count with a join or something like that, right ?

Search::add(Post::class, 'title') ->add(Video::class, 'title') ->startWithWildcard() // Should sort identically match/without wildcard on the top. ->get('os');

Right now it's as such

$results = Search::add(Post::class, 'title')
    ->add(Video::class, 'title')
    ->get('howto');

My users can check what models they want to search, which means the searched models are dynamic. In the above method, there's no way to dynamically search only the models selected by a user. I'm merely suggesting something that works like this.

$models = [
        [Post::class,'title'],
        [Video::class, 'title']
    ];
$results = Search::addMany($models)
    ->get('howto');

Thanks!

Hi,

I will submit this as a PR this time.. I should have time over Christmas to do it :)

Would you be happy with an option to use simplePaginate() vs paginate()? If so, do you have any preference on how it's implemented?

Hello, if you can add type(class_basename or model_name) column each row it will be better solution, how we can handle when we are using API service ? On your example you are using blade but we arent. Can you please add an option to add each row to type. Thanks. @pascalbaljet

Perhaps the package already contains a solution to this problem, but I was not able to find it. Say you have a model (e.g. Post) with a relationship to another model (e.g. Author). In this example use case, the relationship field can be null, meaning that a post has no author. First, a simple search query:

Search::add(Post::class, ['title'])->get();

The query above works fine, showing all posts (including posts with no author) and allowing the user to search using the post title column. If we want to add the ability to search on the author's name, we have to add the related model column to the query using the dot notation.

Search::add(Post::class, ['title', 'author.name'])->get();

This query works, but appears to use an inner join behind the scenes. As a result, all posts without an author are excluded from the results. The desired behavior would be to show all posts (when no search query is used) and all matching posts (when a search query is used), including posts that lack an author but where the title is a match to the search query.

Imagine you have a Users table and a Posts table, where a post belongs to a user.

How could I search at the same time for, say, all users "name" fields AND all users posts 'body' fields at the same time? In other words, how could I use this package to search for all users name that match an "X" search input or users that have a post with a body that matches that same search input?

I want to sort main result set by relation in an order.. eg lets say a post has many tags i want to get all post but they should be sorted by their tags using eager load.

Hi, and thanks for the great lib!

I was hoping to just use it for pagination only, but it's throwing an exception with no search terms. Removing that exception, it works fine - but I wondered if there is a reason for enforcing search terms, and if you think allowing pagination only would be possible?

I'm currently getting around it by searching the created_at column for %- which returns all results, and allows pagination only.#

Happy to contribute a PR, but wanted to check there wasn't a reason against it first. I've not actually looked how you're doing multi-model pagination.

Hi, superb package!

However, I have a problem adding multiple models to the search. I think it has something to do with my implementation. When I run the following code, I get this error message: "Contact" is not a valid backing value for enum App\Enums\ContactType.

<?php

namespace App\Http\Controllers;

use App\Models\Contact;
use App\Models\Person;
use App\Models\Zaak;
use ProtoneMedia\LaravelCrossEloquentSearch\Search;
use Illuminate\Http\Request;
use Illuminate\Http\Response;

class SearchController extends Controller
{
    /**
     * Show search page
     *
     * @param  Request  $request
     * @return Response
     */
    public function __invoke(Request $request)
    {
        $zaak = Zaak::query()
            ->when($request->query('lines'), fn ($query, $lines) => $query->whereIn('lines', $lines))
            ->when($request->query('states'), fn ($query, $states) => $query->whereIn('states', $states))
            ->when($request->query('user'), fn ($query, $user) => $query->where('user_id', $user))
            ->when($request->query('country_from'), fn ($query, $country_from) => $query->where('country_from', $country_from))
            ->when($request->query('country_via'), fn ($query, $country_via) => $query->where('country_via', $country_via))
            ->when($request->query('country_to'), fn ($query, $country_to) => $query->where('country_to', $country_to))
            ->when($request->query('codes'), fn ($query, $codes) => $query->whereIn('codes', $codes));

        $person = Person::query()
            ->when($request->query('created_from'), fn ($query, $created_from) => $query->whereDate('created_at', '>=', $created_from))
            ->when($request->query('created_to'), fn ($query, $created_to) => $query->whereDate('created_at', '<=', $created_to));

        $contact = Contact::query()
            ->when($request->query('created_from'), fn ($query, $created_from) => $query->whereDate('created_at', '>=', $created_from))
            ->when($request->query('created_to'), fn ($query, $created_to) => $query->whereDate('created_at', '<=', $created_to));

        $results = Search::new()
            ->add($zaak, 'description', 'reference')

            // TODO: https://github.com/protonemedia/laravel-cross-eloquent-search/issues/74
            ->add($person, ['name', 'organisation'])
            ->add($contact, ['summary', 'description'])

            ->includeModelType()
            ->beginWithWildcard()
            ->paginate(
                perPage: 10,
                page: $request->query('page', 1)
            )
            ->search($request->query('search', 'verylongunfindablestring'));

        $query = $request->query();
        $results->appends($query);

        return view('search.index', compact('results', 'query'));
    }
}

Can you spot what went wrong?

@pascalbaljet Is it possible to search on pivot table?

I have the following models (participant belongsToMany project),

participants
    id

participant_project 	
    participant_id
    project_id
    first_name
    last_name

projects
    id	

Getting Column not found: 1054 Unknown column 'project_participant.id' in 'field list' error when I try this; as I don't have an id column in the pivot table.

Search::new()
    ->add(\App\Order::whereIn('project_id', $projects), 'confirmation_number')
    ->add(\App\ProjectParticipant::whereIn('project_id', $projects), ['first_name', 'last_name'])
    ->orderByRelevance()
    ->beginWithWildcard()
    ->paginate(20)
    ->search($request->search);

Also, I tried using join, but not working as expected ->add(\App\Participant::join('project_participant', fn($join) => $join->on('participants.id', '=', 'project_participant.participant_id')->where('project_participant.project_id', 8)), ['project_participant.first_name', 'project_participant.last_name'])

Is there any way to achieve this?

Hello,

Love this package!

Any thoughts on how I could use the limit / offset eloquent methods vs paginate? I'm handling pagination a little differently in one project and would like to use this package but without the paginate() method.

Thank you

I kinda need to search in some column that holds html stuff and I must search as

orWhereRaw('regexp_replace(description, "<[^>]*>", "") like ?', "%{$searchTerm}%")
->orWhereRaw('regexp_replace(description, "<[^>]*>", "") like ?', '%' . htmlentities($searchTerm) . '%');

is there any way to make it work?

Hej,

are there any plans to support SQLite3 as database driver? I am developing my apps with SQLite3 on my machine and with MySQL on the production server. So far I cannot use this package as much as I would like to. And I don't think that I would be this hard:

• use LENGTH() instead of CHAR_LENGTH()
• escape column names because SQLite3 does not support a number as the first character of a column name

If you would like I could create a pull request. I only need one hint: where are the columns like 0_post_key are defined? Couldn't find it for now.