Query builder and model behaving differently for date fields

[efecan]

My Notification model is as follows;

use Jenssegers\Mongodb\Eloquent\Model as Eloquent;

class Notification extends Eloquent {

    protected $collection = 'notification';

    protected $dates = ['readDate'];
    protected $guarded = [];

    public $timestamps = false;

}

If I update the model as follows it works fine and saved date is a proper ISODate

Notification::find($id)->update(['readDate' => now()]);

{
    "_id" : ObjectId("5d9ce7970c3e09489a42a4a2"),
    "title" : "test",
    "readDate" : ISODate("2019-10-08T19:46:30.000Z"),
}

But if I make a single update with query builder, the saved date is stored as an object

Notification::where('_id', $id)->update(['readDate' => now()]);

{
    "_id" : ObjectId("5d9ce7970c3e09489a42a4a2"),
    "title" : "test",
    "readDate" : {
        "date" : "2019-10-08 23:56:24.467242",
        "timezone_type" : 3,
        "timezone" : "Europe/Istanbul"
    }
}

Shouldn't both behave same for fields that are defined in $dates array in model definition?

[Smolevich]

@efecan, what do you see in Mongo storage?

[efecan]

@efecan, what do you see in Mongo storage?

The json blocks under the code blocks are directly from mongo.

[Smolevich]

What is the function now()?

[efecan]

What is the function now()?

It is an alias for Carbon::now()
https://laravel.com/docs/5.5/helpers#method-now

I get the same result with Carbon::now()

[SeanDunn123]

The update() function doesn't appear to respect the $dates array. I get the expected result on save() but cannot on update

[mshamaseen]

I'm having a similar behavior where dates are stored as object type in the DB if I use Carbon, but in my case the object in the DB is empty.