updateOne with objectid? about mongo-php-library

[jmikola]

I don't believe this is any different than the legacy driver. The criteria you've defined is attempting to match an _id with the string value "567eba6ea0b67b21dc004687". You likely want to match on new MongoDB\BSON\ObjectID("567eba6ea0b67b21dc004687"). The same applies to other BSON types (e.g. matching on a date field would require you to use our BSON date object in your criteria).

Feel free to close this issue if that resolves it.

[globules-io]

Yup that solves my issue, thank you for replying

[bujardeari]

and how do you import MongoDB\BSON\ObjectID , i have a Slim application and have installet mongodb extension via composer , but it cant find MongoDB\BSON\ObjectID class

[jmikola]

@bujardeari: MongoDB\BSON\ObjectID is provided in the mongodb PECL extension. This is not to be confused with the mongodb/mongodb package. Composer is used for installing packages but does not currently install PECL extensions. That said, it can enforce the mongodb/mongodb package's requirement that the mongodb extension be installed on the system.

If your system does not currently have the mongodb extension installed, please follow one of the installation procedures in the manual. Note that PHP web and CLI environments may have separate configuration files, so it's possible the extension is installed for a CLI environment, which Composer would use for checking requirements, but not a web SAPI where you may be trying to run your application.

In the future, please open a new GitHub issue rather than commenting on an old, closed thread. This will help ensure that your question gets seen and also avoid adding off-topic questions to a previous thread (in this case, the OP was asking about updateOne behavior and your question pertains to a missing class). You can always link back to an old issue for context if that would help.

[bujardeari]

it had it installed, the problem was only that after version 1.3 it was renamed to MongoDB\BSON\ObjectId and the previous one was MongoDB\BSON\ObjectID , and that confused me to try different things until i noticed the change. However thank you for your description

[jmikola]

the problem was only that after version 1.3 it was renamed to MongoDB\BSON\ObjectId and the previous one was MongoDB\BSON\ObjectID

Ah, that was indeed change in 1.3.0 with PHPC-1004. I obviously didn't give that much thought given that I referred to it as "ObjectID" in my last comment 😄

That said, I'm not sure how this came up for you, as class names in PHP are case-insensitive. We would not have made the change otherwise, as it would have been a BC break.

[bujardeari]

I was using it from within a Slim 3 application controller class, and that made the difference.

…

On Tue, 19 Mar 2019 at 13:47, Jeremy Mikola ***@***.***> wrote: the problem was only that after version 1.3 it was renamed to MongoDB\BSON\ObjectId and the previous one was MongoDB\BSON\ObjectID Ah, that was indeed change in 1.3.0 with PHPC-1004 <https://jira.mongodb.org/browse/PHPC-1004>. I obviously didn't give that much thought given that I referred to it as "ObjectID" in my last comment 😄 That said, I'm not sure how this came up for you, as class names in PHP are case-insensitive. We would not have made the change otherwise, as it would have been a BC break. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHecd8KRyT0ux_ARnJ-cUotKDAfdLsd8ks5vYNxzgaJpZM4G7fWR> .

[lindelius]

Until the class files have been either manually included or autoloaded, both namespaces and classes are case-sensitive (except on Windows, I think).

This works

$first = new App\SomeObject(); // <-- Correct case
$second = new App\someobject(); // <-- Incorrect case

This does not

$first = new App\someobject(); // <-- Incorrect case

However, this shouldn't affect the driver classes since they are loaded instantly along with all other extensions (which worked perfectly fine when I just tested).

@bujardeari Are you sure that the extension was properly loaded before when you experienced the class name issue?