updated_at not fully qualified, creates ambiguous column errors

[bryceray1121]

When attempting to use delete() or update() on an eloquent model you can not use any joins because you will get an ambiguous column name error on updated_at. This is because the Eloquent/Builder.php does not prefix updated_at with the proper table name. I attempted to do a pull request for this, but the issue is further complicated by Arr::add (used in addUpdatedAtColumn) doing automatic dot notation exploding. This prevents me from adding a table.columnName string similar to the operation of SoftDeletes trait.

Laravel 5.2

[srmklive]

You can disable $timestamps on specific models by doing this: public $timestamps=false.

One question though, why are you using join when updating or deleting a row? Can you describe in detail the exact scenario?

[themsaid]

There was an attempt to fix a similar issue: #13519
But end up causing problems with Postgres and also sqlite: #13707

So the fix was reverted: d12c4bb

I don't think there'll be an easy solution for this as using a fully qualified column name table.column has different rules between drivers which requires having different implementations.

[troygilbert]

This seems like a pretty major issue. Maybe I'm using Eloquent wrong, but with just a simple use of Eloquent like this: $model->childRelationship()->update(['some_column' => $value]); fails.

[samrap]

Yeah it is definitely an issue. The commit referenced by @themsaid was mine, and while I haven't had the time to revisit this issue I am going to devote the time to look for a fix regardless. Anyone who wants to work together to find a solution, you can find contact info on my profile. Really determined to get this resolved.

[samrap]

The only thing that comes to the top of my head is in the Eloquent Model's getQualifiedUpdatedAtColumn method, checking which driver is being used and determine the value that way.

The more long-term way would probably be defining the Eloquent Builder as an abstract class and then each driver has its own implementation of the addUpdatedAtColumn method. Of course, that would require Laravel to determine the proper Builder at runtime.

[themsaid]

@samrap Did you get the chance to open a PR?

[samrap]

@themsaid Unfortunately not but I'd be happy to work together with you in order to develop a solution. From what I've discovered with this bug it's a much larger issue than it sounds.

[samrap]

@themsaid I don't have experience outside of MySQL but if I get a list of the different qualified column name rules between drivers I think I can handle fixing this issue on my own.

[baoanhng]

This seems to be an edge case and there hasn't been a fix yet.
But we can always attempt to solve with the Query Builder. Join the tables and manually set deleted_at and updated_at.

[themsaid]

@trandaihung that's what I personally do, I tried to fix before but every database driver has different rules for the qualified column name which makes this change pretty major.

[makoru-hikage]

Aw, I've to use Carbon::now()

[iateadonut]

Can a method ->withoutTimestamps() be added for this particular case?

[JordanDalton]

I've ran into this issue today as well.