Repository navigation
Quick question #1
Description
Found your library while checking the version for mongo and I must say I am impressed. I used to just have a trait that I would use to implement a struct that would represent the collection before using another library that, in a way, simplified it abit more (it was wither) but that from my knowledge is out dated until they update to the official mongodb library.
I would like to know what features would be missing from the crate? I havent used it yet but do plan on implementing it into my application and giving a test run but just curious since in your TODO that it says not all features have been implemented.
Activity
alexkornitzer commentedon Jan 17, 2021
Ah so that is laziness on my part I should have documented the TODOs a little better.
In a sense all features are accessible as you can expose and use the original
mongoclient for the parts that have not been wrapped in this crate, but to list things that are not in that immediately come to my mind:aggregatefunction on aCollectionDatabaseand some functions inCollectionI have probably missed some from the above but for the first version of this wrapper we went for the common queries first just in case we need to tweak the design.
The reason for the multi trait breakdown is due to the desire to strongly type the queries, i.e. you can't use collection
Bs filter on collectionA, you can't get insert a document of typeBintoAcollection, etc. By having this breakdown it prevents the need for certain types to be derived if you are only going to interact with collections in certain ways, or if the derive is not powerful enough and the type must be implemented by hand.Any feedback is greatly welcomed as we will not have accounted for everything and are happy to see how it can be improved.