Laravel-mongodb: Store Carbon DateTime ISO object in Sub Json Document in Laravel 5.2 MongoDB

[sharathm89]

I am trying to store Carbon datetime in Sub Json Document but instead of storing in ISO format its storing in different way shown below.

"_id" : ObjectId("5791bc3d6e79d211aa5be019"),
"breakUps" : [ 
   {
        "amount" : 2000,
        "expiry" : {
            "date" : "2016-09-05 06:25:01.000000",
            "timezone_type" : 3,
            "timezone" : "UTC"
        }
    }
],
"updated_at" : ISODate("2016-07-22T06:25:01.576Z"),
"created_at" : ISODate("2016-07-22T06:25:01.576Z")

Instead it should have been stored like ISODate("2016-07-22T06:25:01.576Z") format.

My Eloquent Model class is:

class Configurations extends Eloquent
{
    public $incrementing = false;
    public  $timestamps = true;
    protected $collection = 'configurations';
    protected $dates = array('created_at','updated_at','breakUps.expiry');
}

[aruncnt]

Same problem with we

[ricardo]

You could solve that by creating an embedded model breakUps with
protected $dates = [ 'expiry' ];

[zuljin]

Same problem here. Its seems that in nested array its doesnt work, just in main level

protected $dates = [ 'expiry' ];

neither something like this
protected $dates = [ 'breakUps.expiry' ];

Maybe a custom function that emulate "$dates" when you create/fill the record.

[ricardo]

@zuljin
I solved it by using UTCDateTime instead of Carbon dates.

It works in subdocuments as well. Like this:

'expiry' => new UTCDateTime(strtotime("now") * 1000)

[always-beta]

$model->breakUps['expiry'] = $model->freshTimestamp() worked for me, which used UTCDateTime internally like @ricardo mentioned.

[alagaccia]

Is this still unfixed?

[Tecaa]

Is this still unfixed?

[alagaccia]

it seems still unfixed.

[alagaccia]

Why @jenssegers closed this post?
Is there anybody who knows how to fix it?

[llioor]

$created_at = Carbon::now()->toDateTimeString();
$date = new \MongoDB\BSON\UTCDateTime(new \DateTime($created_at));

Now you can insert $date to mongo

[alagaccia]

It's quite insane using this method.

[kalkin]

Same issue here, with Laravel 7 and latest development HEAD. Why is this issue closed, is there a solution?