Its ok to create a view directly with compass, but if we need to keep the aggregation pipeline in code for reference, like we do in sequelize while writing migrations. So that in the future if we want to update an existing view, it will be helpful. How can we achieve this?
I’m not sure I understand the question, but you can just think of a view as an aggregation pipeline. So in your code you would just have an aggregation pipeline querying your database and that’s what you would come back to when you need to change something.
Its ok to create a view directly with compass, but if we need to keep the aggregation pipeline in code for reference, like we do in sequelize while writing migrations. So that in the future if we want to update an existing view, it will be helpful.
How can we achieve this?
I’m not sure I understand the question, but you can just think of a view as an aggregation pipeline. So in your code you would just have an aggregation pipeline querying your database and that’s what you would come back to when you need to change something.
You can creat an aggregation pipeline using code instead of compass. It achieves the same outcome and you can save your code.
Great work here! Explanation was very clear & the example was well-chosen to make it easily understandable.
Thank you man, I really appreciate the comment. It lets me know these videos actually helped someone out.