61 lines
2.1 KiB
Text
61 lines
2.1 KiB
Text
opam-version: "2.0"
|
|
name: "caqti"
|
|
maintainer: "Petter A. Urkedal <paurkedal@gmail.com>"
|
|
authors: [
|
|
"Petter A. Urkedal <paurkedal@gmail.com>"
|
|
"Nathan Rebours <nathan@cryptosense.com>"
|
|
"Basile Clément"
|
|
]
|
|
license: "LGPL-3.0-or-later WITH LGPL-3.0-linking-exception"
|
|
homepage: "https://github.com/paurkedal/ocaml-caqti/"
|
|
doc: "https://paurkedal.github.io/ocaml-caqti/index.html"
|
|
bug-reports: "https://github.com/paurkedal/ocaml-caqti/issues"
|
|
depends: [
|
|
"alcotest" {with-test & >= "1.5.0"}
|
|
"angstrom" {>= "0.14.0"}
|
|
"bigstringaf"
|
|
"cmdliner" {with-test & >= "1.1.0"}
|
|
"domain-name" {>= "0.2.0"}
|
|
"dune" {>= "3.9"}
|
|
"dune-site"
|
|
"ipaddr" {>= "3.0.0"}
|
|
"logs"
|
|
"lru" {>= "0.3.1"}
|
|
"lwt-dllist"
|
|
"mdx" {with-test & >= "2.3.0"}
|
|
"mtime" {>= "2.0.0"}
|
|
"ocaml" {>= "4.08.0"}
|
|
"odoc" {with-doc}
|
|
"ptime"
|
|
"re" {with-test}
|
|
"tls"
|
|
"uri" {>= "2.2.0"}
|
|
"x509"
|
|
]
|
|
conflicts: [
|
|
"result" {< "1.5"}
|
|
]
|
|
build: [
|
|
["dune" "build" "-p" name "-j" jobs "@install"]
|
|
["dune" "install" "-p" name "--create-install-file" name]
|
|
["dune" "runtest" "-p" name "-j" jobs] {with-test}
|
|
["dune" "build" "@doc" "-p" name "-j" jobs] {with-doc}
|
|
]
|
|
dev-repo: "git+https://github.com/paurkedal/ocaml-caqti.git"
|
|
synopsis: "Unified interface to relational database libraries"
|
|
description: """
|
|
Caqti provides a monadic cooperative-threaded OCaml connector API for
|
|
relational databases.
|
|
|
|
The purpose of Caqti is further to help make applications independent of a
|
|
particular database system. This is achieved by defining a common signature,
|
|
which is implemented by the database drivers. Connection parameters are
|
|
specified as an URI, which is typically provided at run-time. Caqti then
|
|
loads a driver which can handle the URI, and provides a first-class module
|
|
which implements the driver API and additional convenience functionality.
|
|
|
|
Caqti does not make assumptions about the structure of the query language,
|
|
and only provides the type information needed at the edges of communication
|
|
between the OCaml code and the database; i.e. for encoding parameters and
|
|
decoding returned tuples. It is hoped that this agnostic choice makes it a
|
|
suitable target for higher level interfaces and code generators."""
|