In "Mix queries" using the where before the search generates a SQL Error:

SQLSTATE[HY093]: Invalid parameter number: parameter was not defined (SQL: select count(*) as aggregate

moving the where after the search seems to work without issues !

Weird error when using aws elasticsearch

i know aws works because i can use it fine with postman
'config' => [ 'hosts' => ['aws_endpoint'], 'retries' => 1, ],

Usually users do not input operators like (ge)2018-04-16
It make view code little hacky like change values before send

I think operators should be in query keys, not values like below

Now
<input name="foo" value="(ge)2018-04-16">
My opinion
<input name="(ge)foo" value="2018-04-16">

Methods for Lavavel Models:

• saveOrFail
• performInsert
• insertAndSetId
• ???

Hey @czim I'm interested in using this package instead of Stapler, but we already use Stapler (via laravel-stapler) in our project. I saw the list of differences in the readme, but was wondering if there was a more robust migration guide?

If not, is there anything else I should be aware of when attempting the transition? Is the rest of the API mostly the same as stapler's?

This looks far m

User
    affiliate_actions_for_this_user(): AffiliateAction[] <- AffiliateAction.invited_by_user()
    affiliate_action_that_invited_this_user(): AffiliateAction <- AffiliateAction.invited_user()

AffiliateAction
    invited_by_user() via invited_by_user_id: User <- User.affiliate_actions_for_this_user()
    invited_user() via invited_user_id: User <- User.affiliate_action_that_invited_