Its 16mb.
You can use gridfs to store things like movies; that is not the intent of bson but rather a more efficient encoding that json.
So, 16mb of metadata for your movies, or data. Lots of people use (bson) documents to store eg, an order, or a blog post, or a check-in, or a product.
-- Max
I was reading about the 4mb document size limit (which I believe is now either 8mb or 16mb, I'm unsure). I'm pretty confused about this. The whole point of storing data using BSON instead of JSON is to support binary data, but binary data is often much larger than these proposed size limits. For example, a photo or music database (ostensibly two of the most common "kinds" of binary data conceivable) could easily consist almost entirely of files that exceed the apparent MongoDB document size limit.
Am I misunderstanding the role this limit plays? Is it merely a limit on some sort of "meta" data but such that the actual underlying data can be of reasonably large sizes? Or, is MongoDB fundamentally incapable of storing realistic binary files such as images, audio, etc., which obviously can quite frequently exceed the size limits we are discussing here?
I admit, I'm probably totally misunderstanding the situation.
Thank you very much.
New 'n confused,
-Keith
Cheers!
--
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com
To unsubscribe from this group, send email to
mongodb-user...@googlegroups.com
See also the IRC channel -- freenode.net#mongodb