-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supporting multiple mongo backends #42
base: master
Are you sure you want to change the base?
Conversation
…tation named Datasource
updated readme.
The biggest concern is every requests will go through reflection to find the db name which could impact the performance. |
You're absolutely right I just don't know what to do about it other than to try to build up a map of classname -> db names On Oct 20, 2011, at 4:48 PM, Green Luo wrote:
|
Probably code enhancement could be a solution. |
I'll try to take a look into these two approaches next week. On Oct 20, 2011, at 11:02 PM, Green Luo wrote:
|
Conflicts: lib/play-morphia.jar src/play/modules/morphia/Model.java src/play/modules/morphia/MorphiaPlugin.java
…endencies.yml" This reverts commit c58e04d.
I've made an update to improve the performance of the datasource name lookup. Also have added a couple bugfixes and merged in the latest 1.2.4 code. |
thx, will evaluate On Wed, Nov 2, 2011 at 8:05 AM, dbusch <
|
I've modified the plugin so that it can support configuring multiple mongo backends. You can now annotate your model classes to declare in which backend the collection lives. The value given in the annotation matches up with a set of configuration settings in the application.conf file.
Issues: