Web/Databases and Persistence
Below is a list of databases that have been used or designed for web development. See also: Database Interfaces
happstack-state, also referred to as MACID, is a native Haskell persistent data store layer. It stores Haskell datatypes and queries are written in Haskell. Although it is part of the Happstack suite, it does not depend on happstack-server and can easily be used with other web frameworks.
In buzzword terms, happstack-state is a NoSQL, RAM-cloud which can store arbitrary Haskell datatypes.
|Author:||Happstack team, HAppS LLC|
|Maintainer:||Happstack team <email@example.com>|
|Package & repositories||Hackage - Darcs|
HDBC (Haskell Database Connectivity) provides an abstraction layer between Haskell programs and SQL relational databases. This lets you write database code once, in Haskell, and have it work with any number of backend SQL databases (MySQL, Oracle, PostgreSQL, ODBC-compliant databases, etc.)
- HDBC provides an abstraction layer between Haskell programs and SQL relational databases. This lets you write database code once, in Haskell, and have it work with any number of backend SQL databases (MySQL, Oracle, PostgreSQL, ODBC-compliant databases, etc.)
- HDBC is modeled loosely on Perl’s DBI interface, though it has also been influenced by Python’s DB-API v2, JDBC in Java, and HSQL in Haskell.
- HDBC is a from-scratch effort. It is not a reimplementation of HSQL, though its purpose is the same.
|Maintainer:||John Goerzen <firstname.lastname@example.org>|
Persistent is a high-level, non-relational, type-safe persistence layer for Haskell. Its design allows it to be used on both SQL and non-SQL backends. Heavy usage of type families allows strong type guarantees, while usage of template haskell removes the need for boilerplate coding.
|Author:||Michael Snoyman <email@example.com>|
|Maintainer:||Michael Snoyman <firstname.lastname@example.org>|
|Packages & repositories||Hackage - Github|
Takusen is a DBMS access library. Like HSQL and HDBC, we support arbitrary SQL statements (currently strings, extensible to anything that can be converted to a string).
Takusen's unique selling point is safety and efficiency. We statically ensure all acquired database resources - such as cursors, connections, and statement handles - are released, exactly once, at predictable times. Takusen can avoid loading the whole result set in memory, and so can handle queries returning millions of rows in constant space. Takusen also supports automatic marshalling and unmarshalling of results and query parameters. These benefits come from the design of query result processing around a left-fold enumerator.
Currently we fully support ODBC, Oracle, Sqlite, and PostgreSQL.
|Author:||Alistair Bayley, Oleg Kiselyov|
|Packages & repositories||Hackage - Darcs|