Support for objects other than ObjectID/String as ids #12337
Replies: 3 comments
-
Hello @sean-kates! Good to see feature requests! have you seen this, right? I would ask for the MongoDB Driver docs for this API that you are trying to use. I guess we can think a way to make the driver more exposable/flexible to the enduser |
Beta Was this translation helpful? Give feedback.
-
I agree that Meteor should handle other forms of IDs. But first of all, we should start with making sure the |
Beta Was this translation helpful? Give feedback.
-
@radekmie Ah I didn't see this discussion, exactly what I was looking for. I'll test with ObjectIds this week and see how the results look, definitely a good option for compression. The problem there is that we use UUID V5 as a uniqueness check, and I don't believe ObjectIds will accomplish the same thing. We can probably close this one out, as the Mongo team seems to have the discussion covered over there. |
Beta Was this translation helpful? Give feedback.
-
Hello,
Couldn't find any other discussion on this one in feature requests, so apologizes if it's a duplicate.
I'm working on scaling up our application to handle much larger collection sizes, billions of records in some. We are currently using string UUIDs in the _id field. I was researching was to improve compression and performance, and one thing I saw was about using binary UUIDs instead of strings.
https://stackoverflow.com/questions/46327072/performance-gains-to-using-uuid-instead-of-its-string-representation-as-id-on-m
I toyed around with it, but it doesn't look like Meteor supports them.
Are there any plans to allow this in the future? It seems like supporting them would be beneficial for larger scale Meteor applications.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions