Andreas Braun

@medeiroz what purpose does that extra trait serve? Since the original trait itself is opt-in, wouldn't the better solution just be to not include the trait in the first place?

@medeiroz Isn't the `RefreshDatabase` trait itself opt-in, i.e. you have to explicitly use it in your tests to enable its functionality?

@Treggats thanks for confirming. @medeiroz since the trait is opt-in, you shouldn't have to create a separate trait to undo the `RefreshDatabase` functionality; you should just not include the trait...

Please include the versions for laravel-mongodb, your PHP version, and the database server and driver versions in your bug report, as suggested in the issue template. If you run the...

Hi @sanjay-chabhadiya17, thank you for confirming. Based on your description, can you please run the following script and post the output? ```php // Please adjust connection string, database name, and...

Sorry, I lost track of this. Looking at the query, that kind of query should not this amount of time in a properly indexed database, even with a large amount...

Thank you for reporting this! It looks like one way would be to only throw a `QueryException` from the MongoDB connection. However, this is not really desirable, as `QueryException` extends...

> Just run into this problem now, after trying $dates to no success, it seems $casts did the trick. That mainly depends on the version you're using. For the upcoming...

`$lookup` always returns an array of documents that matched; if you are expecting a single document, you need to use `$first` in an `$addFields` stage to unwrap the array: ```...

@Siebov do you call the aggregation pipeline from a model? If so, what does that model have defined as relations for the `user` and `proposal_round` fields?