Create a MySQL connection pool and run the given action. The pool is properly released after the action finishes using it. Note that you should not use the given ConnectionPool outside the action since it may be already been released.

Same as withMySQLPool, but instead of opening a pool of connections, only one connection is opened.

Create a MySQL connection pool. Note that it's your responsibility to properly close the connection pool when unneeded. Use withMySQLPool for automatic resource control.

Default information for setting up a connection.

Defaults are as follows:

• Server on localhost
• User root
• No password
• Database test
• Character set utf8

Use as in the following example:

connect defaultConnectInfo { connectHost = "db.example.com" }

Default (empty) information for setting up an SSL connection.

Information required to connect to a MySQL database using persistent's generic facilities. These values are the same that are given to withMySQLPool.

Mock a migration even when the database is not present. This function will mock the migration for a database even when the actual database isn't already present in the system.

MySQL specific upsert_. This will prevent multiple queries, when one will do. The record will be inserted into the database. In the event that the record already exists in the database, the record will have the relevant updates performed.

Do a bulk insert on the given records in the first parameter. In the event that a key conflicts with a record currently in the database, the second and third parameters determine what will happen.

The second parameter is a list of fields to copy from the original value. This allows you to specify which fields to copy from the record you're trying to insert into the database to the preexisting row.

The third parameter is a list of updates to perform that are independent of the value that is provided. You can use this to increment a counter value. These updates only occur if the original record is present in the database.

More details on HandleUpdateCollision usage

Item
  name        Text
  description Text
  price       Double Maybe
  quantity    Int Maybe

  Primary name

items:
+------+-------------+-------+----------+
| name | description | price | quantity |
+------+-------------+-------+----------+
| foo  | very good   |       |    3     |
| bar  |             |  3.99 |          |
+------+-------------+-------+----------+

name,description,price,quantity
foo,,2.50,6
bar,even better,,5
yes,wow,,

records =
  [ Item { itemName = "foo", itemDescription = ""
         , itemPrice = Just 2.50, itemQuantity = Just 6
         }
  , Item "bar" "even better" Nothing (Just 5)
  , Item "yes" "wow" Nothing Nothing
  ]

items:
+------+-------------+-------+----------+
| name | description | price | quantity |
+------+-------------+-------+----------+
| foo  | very good   |  2.50 |    6     |
| bar  | even better |  3.99 |    5     |
| yes  | wow         |       |          |
+------+-------------+-------+----------+

This type is used to determine how to update rows using MySQL's INSERT ... ON DUPLICATE KEY UPDATE functionality, exposed via insertManyOnDuplicateKeyUpdate in this library.

Since: 2.8.0

Copy the field directly from the record.

Since: 3.0

Copy the field into the database only if the value in the corresponding record is non-NULL.

@since 2.6.2

Copy the field into the database only if the value in the corresponding record is non-empty, where "empty" means the Monoid definition for mempty. Useful for Text, String, ByteString, etc.

The resulting HandleUpdateCollision type is useful for the insertManyOnDuplicateKeyUpdate function.

@since 2.6.2

Copy the field into the database only if the field is not equal to the provided value. This is useful to avoid copying weird nullary data into the database.

The resulting HandleUpdateCollision type is useful for the insertManyOnDuplicateKeyUpdate function.

@since 2.6.2

Open a connection to MySQL server, initialize the SqlBackend and return their tuple

Since: 2.12.1.0