<div dir="ltr">FWIW, +1. Sorry for not speaking up sooner, I just don't have much to add: of the three, I've only used HDBC.<div><br></div><div>Michael<br><br><div class="gmail_quote">On Wed, Jul 7, 2010 at 8:44 PM, Christopher Done <span dir="ltr"><<a href="mailto:chrisdone@googlemail.com">chrisdone@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I did try Takusen with PostgreSQL and it worked perfectly for me, too.<br>
The only reason I'm using HDBC is because there was already a<br>
HaskellDB HDBC driver. I was considering writing a Takusen driver for<br>
HaskellDB, in fact (if possible).<br>
<br>
Anyway, the point remains, we need a single goto database library. I<br>
don't know if Takusen's left-fold typeable way of doing things is<br>
different enough to disqualify it from The Great Merge or not. Though<br>
the lack of response to this thread makes me think no one particularly<br>
thinks this is a problem. Is it worth the effort having one very high<br>
quality stable library instead of three fairly okay<br>
not-really-that-different maybe-working libraries?<br>
<div><div></div><div class="h5"><br>
On 7 July 2010 19:29, Gregory Crosswhite <<a href="mailto:gcross@phys.washington.edu">gcross@phys.washington.edu</a>> wrote:<br>
> I've been using Takusen for all of my database needs, which most of the<br>
> time means interfacing to a PostgreSQL database, and it has worked out<br>
> pretty well in practice. In fact, I experimented with hsql and HDBC a while<br>
> back and for some reason I can't remember they turned out to be less<br>
> convenient than Takusen so I changed the code I was working on back over to<br>
> Takusen.<br>
><br>
> Cheers,<br>
> Greg<br>
><br>
> On 7/7/10 2:17 AM, Nick Rudnick wrote:<br>
>><br>
>> Hi Chris,<br>
>><br>
>><br>
>> these are good questions -- actually, you might have mentioned Takusen,<br>
>> too.<br>
>><br>
>> Clearly, HDBC is the largest of these projects, and there are lots of<br>
>> things well done there.<br>
>><br>
>> Takusen has an interesting approach, and I would like to see a discussion<br>
>> here about the practical outcomes, as I have done no testing yet.<br>
>><br>
>> I myself quite a time ago had an opportunity to do a Haskell job with a<br>
>> PostgreSQL backend for a client, where I tried out all three and got hsql<br>
>> running easiest. A maintainer was vacant, so I stepped in happily -- doing<br>
>> refactorings, fixing problems at request, giving advice to people.<br>
>><br>
>> I can say that I am quite a little PostgreSQL centric and that I have a<br>
>> GIS project in sight, for which I want to try to adapt hsql.<br>
>><br>
>> Cheers,<br>
>><br>
>> Nick<br>
>><br>
>><br>
>> Christopher Done wrote:<br>
>>><br>
>>> One thing that would be nice is a unification of the general database<br>
>>> libraries hsql and HDBC. What is the difference between them? Why are<br>
>>> there two, and why are there sets of drivers for both (duplication of<br>
>>> effort?)? I've used both in the past but I can't discern a real big<br>
>>> difference (I used the hsql-sqlite library and the HDBC-postgresql<br>
>>> library, whichever worked...). It seems the best thing to do is either<br>
>>> actively merge them together and encourage the community to move from<br>
>>> one to the other -- judging from what I've read HDBC is more up to<br>
>>> date and newer than hsql -- or have some documentation with damn good<br>
>>> reasons to choose one or the other, because currently this is a<br>
>>> needless source of confusion and possible duplication of effort for<br>
>>> Haskell's database libraries.<br>
>>><br>
>>> I wasn't going to post until I'd actually researched the difference<br>
>>> myself properly but I didn't get chance to have a look over the<br>
>>> weekend, but I thought I'd pose the question. Do people actually care<br>
>>> about this?<br>
>>> _______________________________________________<br>
>>> Haskell-Cafe mailing list<br>
>>> <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
>>> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
>>><br>
>><br>
>> _______________________________________________<br>
>> Haskell-Cafe mailing list<br>
>> <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
>> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
><br>
> _______________________________________________<br>
> Haskell-Cafe mailing list<br>
> <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
><br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br></div></div>