fix: whereNotLike misses the not in the sql query

[mmachatschek]

At the moment when calling whereNotLike or orWhereNotLike the query is missing the 'not' in the query. This is actually super critical.

Is there a plan to implement something to only apply the where*Like queries of this package if you use laravel/framework < 11.19.0 ? in order to use the "real" implementation of laravel itself

[mmachatschek]

@tpetry i went ahead and also added the "fallback" to the available implementation of laravel if we are on laravel 11.17.0 and above

[tpetry]

Can you explain the fallback you've added? So why you've added that? Because the executed SQL queries should really not be different when a different Laravel version is used.

[mmachatschek]

@tpetry laravel/framework is using the "->whereBasic" call for the Postgres grammer which is wrapping the column in a "column"::text https://github.com/laravel/framework/blob/11.x/src/Illuminate/Database/Query/Grammars/PostgresGrammar.php#L99 thats why I had to update the test as well and use two versions of the implementation. I can update the calls of the package as well to reflect the same behaviour as laravel has.

The "fallback" i added is just using the implementation of laravel itself instead of overriding it. I don't get why the package would override the behaviour when laravel supports it out of the box since 11.17.0. I can revert the commit 4e64ea3 if you want but I'd think it would be better to use the laravel implementation instead of overriding the behaviour.

[tpetry]

I've added the whereLike implementation long before Laravel had it. So when they released it, I had to change my implementation to conform to their implementation. I seem to have missed that they do the text casting on the column.

Please remove the version check and change my implementation to be identical to Laravel's one 😉

[tpetry]

Thanks for writing the fix. And sorry for the inconvenience.