You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running this query inside mongosh it just works fine.
rawclients$updates etc just works fine in mongolite but again using the query above complains about wrong JSON
Ultimate i thought of throwing this query into the $run command, that should work... but also here, complains about JSON
Putting every field name and value inside "" still the JSON problem persists...
Is not working, what am I'm missing here ... al also tried the json command notation like
$run(command = "{\"ping\": 1}", simplify = TRUE) # that works.... instead adding the whole query inside like
$run(command = glue("{\"{query}\"): 1}", simplify = TRUE) # just blows up with a JSON error.
Putting " around every key/value also still fails.
Hope someone has a hint how to run this $type update query...
I'm inserting a large table in tibble format into mongodb that works great :), and after the insert I'm "restoring" the ObjectId's with this query :) During the insert it creates string fields for the foreigner keys I'm using in my document.. no problem expected behaviour but however hope to clean it up afterwards like this :)
JWR
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to execute this query:
Putting every field name and value inside "" still the JSON problem persists...
I'm pretty stuck... why something simple like:
Using build in $update:
Using run:
Is not working, what am I'm missing here ... al also tried the json command notation like
Putting " around every key/value also still fails.
Hope someone has a hint how to run this $type update query...
I'm inserting a large table in tibble format into mongodb that works great :), and after the insert I'm "restoring" the ObjectId's with this query :) During the insert it creates string fields for the foreigner keys I'm using in my document.. no problem expected behaviour but however hope to clean it up afterwards like this :)
JWR
The text was updated successfully, but these errors were encountered: