-
Notifications
You must be signed in to change notification settings - Fork 233
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
Support for Mongoid #5
Comments
This seems like a fine implementation to me, generally. We aim to play with it a bit and see where the cracks are... |
+1 on mongoid support |
So just an update - isotope11's fork has mongo support and we're using it in production, but we never did the work to get it mainline'd because the developer that was working on it isn't here anymore. If anyone wants to get that merged, we'll help any way we can :) |
+1 for Mongoid support. |
Is someone working on implementing Mongoid for Plutus? |
I'm opening this issue in order to keep track of updating / abstracting plutus to support Mongoid. I'd like to take an approach that will support other persistance mechanisms later on (Redis for example)
I think there are a number of questions to address prior to proceeding. I'll try to list a few, and please add any others that you can think of.
I'm not that familiar with Mongoid myself, but I'm under the impression that it is using ActiveModel under the hood, which means that it should already share an interface with ActiveRecord and anything else that extends ActiveModel. That being the case, I'm thinking that we simply have a Factory Class that generates the appropriate impl based on whatever configuration method we choose. Something like:
Controllers and what not then call
Plutus::Factory:::Transaction.new
orPlutus::Factory::Transaction.find(params)
, etc.The text was updated successfully, but these errors were encountered: