You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
first thanks for wp-eloquent, a very useful wrapper!
I want to ask you if there is any particular reason that hasn't allowed you to use MySqlGrammar (instead of Grammar base class).
By doing a couple of quick tests I noticed that using MySqlGrammar as Grammar use Illuminate\Database\Query\Grammars\MySqlGrammar as Grammar;
and commenting in Database:: bind_params $ query = str_replace ('"', '', $ query);`
which generates wrong sql for json statements (due to the quotes) you could use Laravel's JSON Where clauses
For example: Social::where ('meta->facebook->account->email', '[email protected]')->get ();
The text was updated successfully, but these errors were encountered:
Hello,
first thanks for wp-eloquent, a very useful wrapper!
I want to ask you if there is any particular reason that hasn't allowed you to use MySqlGrammar (instead of Grammar base class).
By doing a couple of quick tests I noticed that using MySqlGrammar as Grammar
use Illuminate\Database\Query\Grammars\MySqlGrammar as Grammar;
and commenting in Database:: bind_params
$ query = str_replace ('"', '
', $ query);`which generates wrong sql for json statements (due to the quotes) you could use Laravel's JSON Where clauses
For example:
Social::where ('meta->facebook->account->email', '[email protected]')->get ();
The text was updated successfully, but these errors were encountered: