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
I'm taking a look to the library to decide if I'm able to use it in existing project. For now it's quite tricky for me to understand how to create separate migrations for inherited documents. For example, I have migration for class AAA, it's works ok, and now I whant to create migration for class BBB (inherited from AAA). The tricky part is that migration for BBB also trying to migrate documents with type AAA (also for CCC, DDD and so on), not only for BBB
For now I'm solving this behavior by cheking and comparing the "_id" value, but would be greate to make it more simple and dynamic. It it possible at all now?
P.S. There is no way to drop (or replace by aggregation) the documents inheritance at my project
Thank you
The text was updated successfully, but these errors were encountered:
Hi and thanks for the great work!
I'm taking a look to the library to decide if I'm able to use it in existing project. For now it's quite tricky for me to understand how to create separate migrations for inherited documents. For example, I have migration for class AAA, it's works ok, and now I whant to create migration for class BBB (inherited from AAA). The tricky part is that migration for BBB also trying to migrate documents with type AAA (also for CCC, DDD and so on), not only for BBB
For now I'm solving this behavior by cheking and comparing the "_id" value, but would be greate to make it more simple and dynamic. It it possible at all now?
P.S. There is no way to drop (or replace by aggregation) the documents inheritance at my project
Thank you
The text was updated successfully, but these errors were encountered: