Skip to content
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

PostgreSQL storage backend #39

Closed
marcelog opened this issue Dec 11, 2013 · 4 comments · Fixed by #101
Closed

PostgreSQL storage backend #39

marcelog opened this issue Dec 11, 2013 · 4 comments · Fixed by #101
Assignees
Labels

Comments

@marcelog
Copy link
Member

No description provided.

@AxisOfEval
Copy link
Contributor

Will Glozer's code is no longer maintained. Fortunately (and unfortunately) there many forks. Here are some that hold promise:

  1. https://github.com/epgsql/epgsql/ - This one aims to be the canonical source and has a mailing list, which is good. I haven't used it personally though.
  2. https://github.com/opscode/epgsql - This fork is by opscode. It is being used in production with sqerl - a DB abstraction library inspired by eprecs (now sumo_db). sqerl is being used in production for chef I guess.

OTOH, semiocast has done their own library called pgsql. Repo here. I've used it with success in initial dabbles in a basic ORM. However, it has deprecated the ODBC approach - but it also adds OTP upgrades which is a good thing. Unfortunately, it misses a LICENSE file. So we might have to ask them to put one in before consideration.

In short, its ghetto-land. Alternatively, we could do our own fork cherry-picking the features we want as PostgreSQL evolves and increases its NoSQL footprint. This will result in a slow start but might prove to be a good option long term. I guess it will be better to see if some other teams are ready to co-operate first. That might prove to be the best of both worlds...

There might be other popular forks/projects as well that I might not be aware of. Think it will be a good idea to enumerate them here before we get started and settle on something.

@AxisOfEval
Copy link
Contributor

Though I can't wait to get started on the PostgreSQL backend, I think we should sort out #60, #61, #62, #38, #23, before starting here.

I have pinged the good guys at semiocast about the missing LICENSE file for their project. Meanwhile, maybe someone at inaka can make a decision about which driver to use by then.

If you ask me I'd choose semiocast's pgsql as it is well written, maintained and tested. I even have a feeling it might become the de-facto standard. 😀

@jfacorro
Copy link
Contributor

This branch has started work on pgsql support using epgsql. Putting it on hold for now.

@AxisOfEval
Copy link
Contributor

@jfacorro Sorry, to chime in so late. Was traveling and had very little time. The situation should change in a day or two and I will have time to concentrate on sumo_db again :)

I can see you've started with epgsql; we can continue down that road.

Thanks and Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants