-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with columns mapping #2
Comments
@jarektkaczyk any news? |
@pvm - Jarek's Eloquence repos aren't heavily-maintained. However, in my view these vanity functions aren't tremendously important. I.e: |
@pvm do I get it right that dynamic wheres don't work for you? Or both examples you provided? If the first is true, then I just strongly suggest not using dynamic wheres - they are very bad concept and lead to issues. @jsdtaylor thanks for chiming in. True, I don't have much time for maintenance, and will be more than happy to share this responsibility with others :) |
Just saying that dynamic where does not work, but where with multiple options too (this we use a lot):
|
@jarektkaczyk any news about it? If you don't have time, I'll try to help and send you a PR. |
@pvm would be lovely 👍 |
only select support? when I use get($columns) or first($columns), the mapping is not working |
Hi,
I have issuing some problems with column mapping.
Example with dynamic where:
Foo::whereId(1);
Example with where:
Foo::where([ ['foo', '=', 'bar'] ])->first();
the mapping is not working. The query is generated with old column name.
Model:
`class Foo extends Model
{
use Eloquence, Mappable;
}`
The text was updated successfully, but these errors were encountered: