Append table name to Builder to prevent conflicting IDs in SQL query

[kyranb]

Fixes the issue "Column 'id' in where clause is ambiguous" when using additional scopes.

Example query that fails due to not specifying the table name for id:

SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'id' in where clause is ambiguous (SQL: select users.*, tenants_user.team_id as pivot_team_id, tenants_user.user_id as pivot_user_id, tenants_user.created_at as pivot_created_at, tenants_user.updated_at as pivot_updated_at from users inner join tenants_user on users.id = tenants_user.user_id where tenants_user.team_id = 2 and id = 1 and users.deleted_at is null limit 1)

[kyranb]

@mpociot

[rodriguezaitor]

Same issue here..

[kyranb]

@mpociot Can this be merged in? I've been using the fork without issue in production for almost 1 year now :)

[okaufmann]

@kyranb when the tests are green, we will consider merging it.

[kyranb]

@okaufmann Can you take a look? I'm not that familiar with mockery, but it looks like just the table name (users) needs to be added in somewhere as the query now includes that.

[okaufmann]

@kyranb please merge the current master in your feature branch so the latest test actions can run again.

[kyranb]

@okaufmann Sorry for the delay here Oliver. I've just done so :)

[kyranb]

@okaufmann @mpociot Can this be reviewed or merged?

[kyranb]

@mpociot @okaufmann Bump :)

[kyranb]

Thanks @Jamesking56 👍