There are three active database libraries: HDBC, HSQL and Takusen. It is quite disappointing from my point of view. Recently there was the same situation with the GUI libraires. The Haskell Community is quite small to waste efforts, developing different libraries for the same things. When I started with HSQL there were only two database libraries: HaSQL for ODBC and libpq for PostgreSQL. They both are dead, I think. I decided that it is useful to have one abstract API that can cover all database bindings. I imagine something like JDBC, ADO or DBI for Haskell. If you guys would like this to happen then lets discuss what we want. I would be happy to work on single project that can satisfy all needs.
Cheers, Krasimir 2006/1/10, Tim Docker <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] wrote: > > > Incidentally, the difficulty with finalizers was precisely the > > argument for using enumerators rather than cursors in database > > APIs. Takusen has implemented that idea; takusen currently supports > > Sqlite, PostgreSQL and Oracle, has a test suite. Its performance test > > shows that takusen can retrieve 2 million rows from a table without > > running out of memory. > > The differences between HDBC and HSQL have been recently discussed. > Where > does Takusen fit into this picture? From the above, it sounds like it > has > quite a different API. Are all 3 of these actively maintained? > > As someone who may wish to construct a haskell db binding for a new db, > it's > not clear to which API it should conform. Sometimes choice is a > burden... > > Tim > > _______________________________________________ > Haskell mailing list > Haskell@haskell.org > http://www.haskell.org/mailman/listinfo/haskell > _______________________________________________ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
