-
Notifications
You must be signed in to change notification settings - Fork 0
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
Project status #1
Comments
It's very dead, unfortunately, and I don't have any plans to use RethinkDB or update it in the near future. Also, unfortunate is that I've yet to find a RethinkDB library for the BEAM that works properly and for modern RethinkDB versions. I could maybe be convinced to work on it more if someone else had real use case. |
Thanks for the update. I'll see if I can get going with what you've done already. With a bit of luck I may be able to extend it and even contribute back at some stage in the future. |
Sounds great! I'll try to answer any questions that come up, too. It's been a while since I've looked at this code, so I make no promises regarding it's usability nor correctness 😄 |
Now I have a pet project for which RethinkDB would be a great fit, so I'm going to be working on this in my free time. |
I've been doing some serious refactoring, some of which is pushed to the develop branch. I'm still working out the new handshake for |
That's great. I have been using the Haskell driver more recently but would certainly come back to take a look at what you have done with lfe. Appreciate your time and effort. |
I was wondering whether you have any future plans for this project.
Having used the Clojure RethinkDB client and had a great experience with it I was encouraged to see that it was the inspiration for this project.
Do you plan to get lfe-rethinkdb to a state similar to that of the Clojure driver?
It would also be great to see some general usage instructions in the README and maybe even example projects or code snippets.
I appreciate the effort you've put into this thus far and look forward to hearing about your plans.
The text was updated successfully, but these errors were encountered: