-
Notifications
You must be signed in to change notification settings - Fork 274
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
mongo db support #473
Comments
It's not for me to decide, but I would note that Surveyor's logic is very tied up in its relational representation of the survey and responses. Porting it to Mongo would entail either an inefficient lots-of-small-documents Mongo model or a very extensive rewrite. The former doesn't seem worth the effort. The latter would a lot of work for a small gain — you might as well create a new project instead. |
Can I use same logic of surveyor if possible? |
You are welcome to if you can make it work. (Surveyor is MIT-licensed, so you can do basically whatever you want so long as you maintain the original license notification.) What I was trying to communicate earlier is that the actual implementation of the logic in Surveyor is very bound up in a relational representation. So it might be more work to reuse Surveyor's implementation than it would be to just build something from scratch on top of Mongo. |
@pform I am considering moving a survey site from Rails to Meteor JS. If I do I would be writing a light weight mongo db version of surveyor. Message me if that meets your needs and if you have interest. |
Can we have mongo db support in future? should I start working on that ?
The text was updated successfully, but these errors were encountered: