Skip to content

Updating with updated_at column triggers some weird behaviour #1726

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

Closed
wants to merge 4 commits into from
Closed

Updating with updated_at column triggers some weird behaviour #1726

wants to merge 4 commits into from

Conversation

rennokki
Copy link
Contributor

@rennokki rennokki commented Mar 8, 2019

Closes #1720

The initial PR on laravel/framework that broke things: laravel/framework#27791

I decided to revert the changes and fix PHPUnit 7.5 void hints.

@Smolevich
Copy link
Contributor

Smolevich commented Mar 10, 2019

@rennokki, this changes has here plus fixes this problem job on your PR

@rennokki
Copy link
Contributor Author

Lovely. Then I'll close this PR :D

@rennokki rennokki closed this Mar 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MongoDB\Driver\Exception\BulkWriteException: Updating the path 'my_collection.updated_at' would create a conflict at 'my_collection'
3 participants