The persistent-mysql-haskell package

[Tags:library, mit, program]

This package contains a backend for persistent using the MySQL database server. Internally it uses the mysql-haskell package in order to access the database. See for more.

This package supports only MySQL 5.1 and above. However, it has been tested only on MySQL 5.5. Only the InnoDB storage engine is officially supported.

Known problems:

[Skip to Readme]


Change log
Dependencies aeson (>=0.6.2), base (>=4.6 && <5), bytestring (>=0.9), conduit (>=0.5.3), containers (>=0.2), io-streams (>=1.2 && <2.0), monad-control (>=0.2), monad-logger, mysql-haskell (>= && <1.0), network (>=2.3 && <3.0), persistent (>=2.6.1 && <3), persistent-mysql-haskell, persistent-template, resource-pool, resourcet (>=0.4.10), text (>=, time (>=1.5.0), tls (>=1.3.5 && <1.4), transformers (>=0.2.1) [details]
License MIT
Author Naushadh <>, Felipe Lessa <>, Michael Snoyman
Maintainer Naushadh <>
Category Database, Yesod
Home page
Bug tracker
Source repository head: git clone git:// -b persistent-mysql-haskell(persistent-mysql-haskell)
Uploaded Fri Apr 14 18:17:06 UTC 2017 by naushadh
Distributions NixOS:, Stackage:
Downloads 205 total (8 in the last 30 days)
0 []
Status Docs available [build log]
Last success reported on 2017-04-14 [all 1 reports]
Hackage Matrix CI




Maintainer's Corner

For package maintainers and hackage trustees

Readme for persistent-mysql-haskell

Readme for persistent-mysql-haskell-


hackage version

A pure haskell backend for persistent using the MySQL database server. Internally it uses the mysql-haskell driver in order to access the database.

See example/Main.hs for how this MySQL backend can be used with Persistent.


persistent-mysql uses mysql (via mysql-simple) as the database driver. mysql is a haskell FFI wrapper for mysqlclient written in C.

Reasons to use a pure haskell driver:

  • mysql has concurrency issues as noted by @feuerbach.

  • mysql-haskell, a pure haskell driver by @winterland1989, outperforms mysql-simple in benchmarks (see hackage or project repo).

  • better portability and possible static compilation of an entire project that uses persistent-mysql.

Personal experience on replacing mysql-simple with mysql-haskell in a project:

  • Performance gains consistent with benchmark.

  • Smoother deployment to Amazon AMI/EC2, since mysql appears to have a hard dependency on the oracle version of libmysqlclient that does not work with the open source variant that is available by default on EC2 (and possibly on other cloud providers).

Potential issues moving from persistent-mysql to persistent-mysql-haskell

ConnectInfo and defaultConnectInfo are not the same between mysql and mysql-haskell, therefore this package is not a 100% drop in replacement for persistent-mysql from the connection configuration perspective.

  • mysql-haskell does not allow provide an API for the entirety of mysqlclient options. Therefore neither can this package.

  • Given the inevitable incompatibility with persistent-mysql, and in the interest of providing a forward-compatible API, ConnectInfo internals and defaultConnectInfo have been deprecated. However the similar utility can be achieved like so:

    import Database.Persist.MySQL
    connectInfo :: MySQLConnectInfo
    - connectInfo = defaultConnectInfo
    -             { connectHost     = "localhost"
    -             , connectUser     = "test"
    -             , connectPassword = "test"
    -             , connectDatabase = "test"
    -             }
    + connectInfo = mkMySQLConnectInfo "localhost" "test" "test" "test"
    connectInfoNewPort :: MySQLConnectInfo
    - connectInfoNewPort = connectInfo { connectPort = 3307 }
    + connectInfoNewPort = setMySQLConnectInfoPort 3307 connectInfo
    connectInfoNewCharSet :: MySQLConnectInfo
    - connectInfoNewCharSet = connectInfo { connectOptions = [CharsetName "utf8"] }
    + connectInfoNewCharSet = setMySQLConnectInfoCharset 33 connectInfo

Aside from connection configuration, persistent-mysql-haskell is functionally on par with persistent-mysql (as of writing this). This can be seen by comparing persistent-test between this fork and upstream.


Why isn't this part of the main/upstream persistent repo?

persistent-mysql supports X but persistent-mysql-haskell API doesn't. Why?

  • Internals (getters/setters) of MySQLConnectInfo and defaultConnectInfo are intentionally masked for forward compatibility.

  • For all others, feel free to open an issue and/or submit a PR.

Does persistent-mysql-haskell ship with tests?

  • It does! :) persistent-test is fully re-used with an additional flag to specifically test persistent-mysql-haskell.

    stack test persistent-test --flag persistent-test:mysql_haskell