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 was wondering, if it is possible to use requery in a multi module architecture where different modules may have their own tables.
The problem I'm facing is that I'm working on a modular Android application, where different features are horizontally separated into different modules. Now, all this modularization makes no sense if in the end the database module depends on all of these feature modules, so I'm wondering if it is possible to have a "main" database module where other modules can be dynamically plugged into. I don't want to have a "god database module", but I don't want to have one database per feature either.
The problem I'm facing is being described pretty well in this IO/19 talk.
I did some digging and found that it may be possible to solve the issue by using the EntityModelBuilder to collect all entities of all active modules and use the resulting Model instead of Models.DEFAULT when creating a DataSource?
Does anyone have experience in this and/or tell me if I'm on the right track?
PS: Great work! I really like requery :)
The text was updated successfully, but these errors were encountered:
Currently this isn't possible as the processor can only work on one module at a time, but there maybe some way to make this work by generating the model in a different module. However there does have to be at least one module that references all the other modules where the model links get generated.
Hi everyone!
I was wondering, if it is possible to use requery in a multi module architecture where different modules may have their own tables.
The problem I'm facing is that I'm working on a modular Android application, where different features are horizontally separated into different modules. Now, all this modularization makes no sense if in the end the database module depends on all of these feature modules, so I'm wondering if it is possible to have a "main" database module where other modules can be dynamically plugged into. I don't want to have a "god database module", but I don't want to have one database per feature either.
The problem I'm facing is being described pretty well in this IO/19 talk.
I did some digging and found that it may be possible to solve the issue by using the EntityModelBuilder to collect all entities of all active modules and use the resulting Model instead of Models.DEFAULT when creating a DataSource?
Does anyone have experience in this and/or tell me if I'm on the right track?
PS: Great work! I really like requery :)
The text was updated successfully, but these errors were encountered: