[erlang-questions] PosegreSQL driver

Tristan Sloughter tristan.sloughter@REDACTED
Mon Mar 11 21:02:52 CET 2013

That is why I sent my original email. There are some patches that forks
have done are design/feature decisions that can't necessarily be merged
together, but a lot can.

I didn't want to simply make tsloughter/epgsql and merge them together
without reaching out to those with the forks since then it would just end
up being another fork from wg/egpsql like all the rest.

Not sure how to move forward with this. Though I'm trying out semiocast's
client now as well.

I think it also shows an issue that I was talking about in #erlounge
yesterday. It would be great to have a page on erlang.org that breaks apps
into categories (json parser, http client, postgres/mysql drivers, ...) and
links to their source on github. But apps that are known to work and be
still in use, not just anything that shows up in a google or github search.


On Thu, Mar 7, 2013 at 10:00 AM, Max Lapshin <max.lapshin@REDACTED> wrote:

> What should I do this weekend? Take a beer, write postgresql erlang driver
> or just write my own nosql database?
> It is really interesting: why are there so many forks? Is it possible to
> consolidate all efforts? Maybe it is impossible at all because different
> drivers implement different approaches of querying async database from
> async erlang?
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130311/3c147dae/attachment.htm>

More information about the erlang-questions mailing list