Meet Donald.
If you're a programmer and have used a database, he's impacted your life in a big way.
This library is named after him.
Honorable mention goes to @dsyme another important Donald and F#'s BDFL.
Donald is a well-tested library that aims to make working with ADO.NET safer and a lot more succinct. It is an entirely generic abstraction, and will work with all ADO.NET implementations.
If you came looking for an ORM (object-relational mapper), this is not the library for you. And may the force be with you.
- Support all ADO implementations.
- Provide a succinct API for interacting with databases.
- Enable asynchronuos workflows.
- Provide explicit error flow control.
- Make object mapping easier.
- Improve data access performance.
Install the Donald NuGet package:
PM> Install-Package Donald
Or using the dotnet CLI
dotnet add package Donald
open Donald
type Author = { FullName : string }
module Author =
let ofDataReader (rd : IDataReader) : Author =
{ FullName = rd.ReadString "full_name" }
let authors : Result<Author list, DbError> =
let sql = "
SELECT full_name
FROM author
WHERE author_id = @author_id"
let param = [ "author_id", SqlType.Int 1 ]
use conn = new SQLiteConnection "{your connection string}"
conn
|> Db.newCommand sql
|> Db.setParams param
|> Db.query Author.ofDataReader
For this example, assume we have an IDbConnection
named conn
:
Reminder: Donald will work with any ADO implementation (SQL Server, SQLite, MySQL, Postgresql etc.).
Consider the following model:
type Author =
{ AuthorId : int
FullName : string }
module Author -
let ofDataReader (rd : IDataReader) : Author =
{ AuthorId = rd.ReadInt32 "author_id"
FullName = rd.ReadString "full_name" }
Important: Donald is set to use
CommandBehavior.SequentialAccess
by default. See performance for more information.
let sql = "SELECT author_id, full_name FROM author"
// Fluent
conn
|> Db.newCommand sql
|> Db.query Author.ofDataReader // Result<Author list, DbError>
// Expression
dbCommand conn {
cmdText sql
}
|> Db.query Author.ofDataReader // Result<Author list, DbError>
// Async
conn
|> Db.newCommand sql
|> Db.Async.query Author.ofDataReader // Task<Result<Author list, DbError>>
let sql = "SELECT author_id, full_name FROM author"
// Fluent
conn
|> Db.newCommand sql
|> Db.setParams [ "author_id", SqlType.Int 1 ]
|> Db.querySingle Author.ofDataReader // Result<Author option, DbError>
// Expression
dbCommand conn {
cmdText sql
cmdParam [ "author_id", SqlType.Int 1]
}
|> Db.querySingle Author.ofDataReader // Result<Author option, DbError>
// Async
conn
|> Db.newCommand sql
|> Db.setParams [ "author_id", SqlType.Int 1 ]
|> Db.Async.querySingle Author.ofDataReader // Task<Result<Author option, DbError>>
let sql = "INSERT INTO author (full_name)"
let param = [ "full_name", SqlType.String "John Doe" ]
// Fluent
conn
|> Db.newCommand sql
|> Db.setParams param
|> Db.exec // Result<unit, DbError>
// Expression
dbCommand conn {
cmdText sql
cmdParam param
}
|> Db.exec // Result<unit, DbError>
// Async
conn
|> Db.newCommand sql
|> Db.setParams param
|> Db.Async.exec // Task<Result<unit, DbError>>
let sql = "INSERT INTO author (full_name)"
let param =
[ "full_name", SqlType.String "John Doe"
"full_name", SqlType.String "Jane Doe" ]
// Fluent
conn
|> Db.newCommand sql
|> Db.execMany param
// Expression
dbCommand conn {
cmdText sql
}
|> Db.execMany param
// Async
conn
|> Db.newCommand sql
|> Db.Async.execMany param
let sql = "INSERT INTO author (full_name)"
let param = [ "full_name", SqlType.String "John Doe" ]
// Fluent
conn
|> Db.newCommand sql
|> Db.setParams param
|> Db.exec // Result<unit, DbError>
// Expression
dbCommand conn {
cmdText sql
cmdParam param
}
|> Db.exec // Result<unit, DbError>
// Async
conn
|> Db.newCommand sql
|> Db.setParams param
|> Db.Async.exec // Task<Result<unit, DbError>>
Donald exposes most of it's functionality through dbCommand { ... }
and the Db
module. But three IDbTransaction
type extension are exposed to make dealing with transactions safer:
TryBeginTransaction()
opens a new transaction or raisesCouldNotBeginTransactionError
TryCommit()
commits a transaction or raisesCouldNotCommitTransactionError
and rolls backTryRollback()
rolls back a transaction or raisesCouldNotRollbackTransactionError
// Safely begin transaction or throw CouldNotBeginTransactionError on failure
use tran = conn.TryBeginTransaction()
let insertSql = "INSERT INTO author (full_name)"
let param = [ "full_name", SqlType.String "John Doe" ]
let insertCmd = dbCommand conn {
cmdText insertSql
cmdParam param
cmdTran tran
}
let selectSql = "SELECT author_id, full_name FROM author WHERE full_name = @full_name"
let selectCmd = dbCommand conn {
cmdText selectSql
cmdParam param
cmdTran tran
}
// Execute commands
let result = dbResult {
do! insertCmd |> Db.exec
return! selectCmd |> Db.querySingle Author.ofDataReader
}
// Attempt to commit, rollback on failure and throw CouldNotCommitTransactionError
tran.TryCommit()
At the core of Donald is a computation expression for building DbUnit
instances, which encapsulate IDbCommand
allowing additional properties to be configured prior to execution. It exposes five modification points:
cmdText
- SQL statement you intend to execute (default:String.empty
).cmdParam
- Input parameters for your statement (default:[]
).cmdType
- Type of command you want to execute (default:CommandType.Text
)cmdTran
- Transaction to assign to command.cmdTimeout
- The maximum time a command can run for (default: underlying DbCommand default, usually 30 seconds)cmdBehavior
- TheCommandBehavior
setting for theDbUnit
(default:CommandBehavior.SequentialAccess
).
To make obtaining values from reader more straight-forward, 2 sets of extension methods are available for:
- Get value, automatically defaulted
- Get value as
option<'a>
If you need an explicit
Nullable<'a>
you can useOption.asNullable
.
Assuming we have an active IDataReader
called rd
and are currently reading a row, the following extension methods are available to simplify reading values:
rd.ReadString "some_field" // string -> string
rd.ReadBoolean "some_field" // string -> bool
rd.ReadByte "some_field" // string -> byte
rd.ReadChar "some_field" // string -> char
rd.ReadDateTime "some_field" // string -> DateTime
rd.ReadDecimal "some_field" // string -> Decimal
rd.ReadDouble "some_field" // string -> Double
rd.ReadFloat "some_field" // string -> float32
rd.ReadGuid "some_field" // string -> Guid
rd.ReadInt16 "some_field" // string -> int16
rd.ReadInt32 "some_field" // string -> int32
rd.ReadInt64 "some_field" // string -> int64
rd.ReadBytes "some_field" // string -> byte[]
rd.ReadStringOption "some_field" // string -> string option
rd.ReadBooleanOption "some_field" // string -> bool option
rd.ReadByteOption "some_field" // string -> byte option
rd.ReadCharOption "some_field" // string -> char option
rd.ReadDateTimeOption "some_field" // string -> DateTime option
rd.ReadDecimalOption "some_field" // string -> Decimal option
rd.ReadDoubleOption "some_field" // string -> Double option
rd.ReadFloatOption "some_field" // string -> float32 option
rd.ReadGuidOption "some_field" // string -> Guid option
rd.ReadInt16Option "some_field" // string -> int16 option
rd.ReadInt32Option "some_field" // string -> int32 option
rd.ReadInt64Option "some_field" // string -> int64 option
rd.ReadBytesOption "some_field" // string -> byte[] option
Donald exposes DbError
type to represent failure at different points in the execution-cycle, all of which are encapsulated within a general DbFailureException
.
type DbError =
| DbConnectionError of DbConnectionError
| DbTransactionError of DbTransactionError
| DbExecutionError of DbExecutionError
| DataReaderCastError of DataReaderCastError
| DataReaderOutOfRangeError of DataReaderOutOfRangeError
exception DbFailureException of DbError
During command execution failures the Error
case of Result
contains one of DbError
union cases with relevant data.
/// Details of failure to connection to a database/server.
type DbConnectionError =
{ ConnectionString : string
Error : exn }
/// Details the steps of database a transaction.
type DbTransactionStep = TxBegin | TxCommit | TxRollback
/// Details of transaction failure.
type DbTransactionError =
{ Step : DbTransactionStep
Error : exn }
/// Details of failure to execute database command.
type DbExecutionError =
{ Statement : string
Error : DbException }
/// Details of failure to cast a IDataRecord field.
type DataReaderCastError =
{ FieldName : string
Error : InvalidCastException }
/// Details of failure to access a IDataRecord column by name.
type DataReaderOutOfRangeError =
{ FieldName : string
Error : IndexOutOfRangeException }
It's important to note that Donald will only raise exceptions in exceptional situations.
By default, Donald will consume IDataReader
using CommandBehavior.SequentialAccess
. This allows the rows and columns to be read in chunks (i.e., streamed), but forward-only. As opposed to being completely read into memory all at once, and readable in any direction. The benefits of this are particular felt when reading large CLOB (string) and BLOB (binary) data. But is also a measureable performance gain for standard query results as well.
The only nuance to sequential access is that columns must be read in the same order found in the SELECT
clause. Aside from that, there is no noticeable difference from the perspective of a library consumer.
Configuring CommandBehavior
can be done two ways:
let sql = "SELECT author_id, full_name FROM author"
// Fluent
conn
|> Db.newCommand sql
|> Db.setCommandBehavior CommandBehavior.Default
|> Db.query Author.ofDataReader
// Expression
dbCommand conn {
cmdText sql
cmdBehavior CommandBehavior.Default
}
|> Db.query Author.ofDataReader
There's an issue for that.
Built with ♥ by Pim Brouwers in Toronto, ON. Licensed under Apache License 2.0.