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
One of the performance issues in Lelylan lies in the fact that when the type changes its properties, all devices properties needs to be updated (this doesn't smell good). This is a bad practice as the type should be living by its own and never be changed, but right now this could happen.
To solve this problem we experimented one shot query on mongodb, which we finally found out not being possible for now, as there is a BUG that will be solved only on version 2.3.2 (at the moment of writing we are at v2.2.0). Here is the code that should work for future improvements. For now we will simply work one record at time.
One of the performance issues in Lelylan lies in the fact that when the type changes its properties, all devices properties needs to be updated (this doesn't smell good). This is a bad practice as the type should be living by its own and never be changed, but right now this could happen.
To solve this problem we experimented one shot query on mongodb, which we finally found out not being possible for now, as there is a BUG that will be solved only on version 2.3.2 (at the moment of writing we are at v2.2.0). Here is the code that should work for future improvements. For now we will simply work one record at time.
Then, to add the code to MongoID you only need to call the collection method.
To create the test suite run the following commands (a type must exist).
Learn more reading
The text was updated successfully, but these errors were encountered: