Request specification.
A Caqti request is a function to generate a query string from information about the driver, along with type descriptors to encode parameters and decode rows returned from the same query. Requests are passed to Caqti_connection_sig.S.call
or one of its shortcut methods provided by a database connection handle.
The request often represent a prepared query, in which case it is static and can be defined directly in a module scope. However, an optional oneshot
parameter may be passed to indicate a dynamically generated query.
Primitives
type ('a, 'b, +'m) t constraint 'm = [< `Zero | `One | `Many ]
A request specification embedding a query generator, parameter encoder, and row decoder.
'a
is the type of the expected parameter bundle.'b
is the type of a returned row.'m
is the possible multiplicities of returned rows.
create arg_type row_type row_mult f
is a request which takes parameters of type arg_type
, returns rows of type row_type
with multiplicity row_mult
, and which sends query strings generated from the query f di
, where di
is the Caqti_driver_info.t
of the target driver. The driver is responsible for turning parameter references into a form accepted by the database, while other differences must be handled by f
.
param_type req
is the type of parameter bundles expected by req
.
row_type req
is the type of rows returned by req
.
row_mult req
indicates how many rows req
may return. This is asserted when constructing the query.
val query_id : ('a, 'b, 'm) t -> int option
If req
is a prepared query, then query_id req
is Some id
for some id
which uniquely identifies req
, otherwise it is None
.
query req
is the function which generates the query of this request possibly tailored for the given driver.
New Convenience Interface
module Infix : sig ... end
The following operators provides a more visually appealing way of expressing requests. They are implemented in terms of create
and Caqti_query.of_string_exn
.
Old Convenience Interface
The following interface will likely be deprecated in the near future and removed in the next major release. For new code it is recommendable to use Infix
operators for high-level usage and create
for low-level usage.
In the following functions, queries are written out as plain strings with the following syntax, which is parsed by Caqti into a Caqti_query.t
object before being passed to drivers. The syntax used by these functions are similar but not the same as the new parser used by the Infix
operators, but it is less strict about which characters may follow a ?
parameter reference, and it treats dollar quotes differently in that "$<var>$"
is left unchanged, and "$$"
is translated as a literal "$"
.
create_p arg_type row_type row_mult f
is a request which takes parameters of type arg_type
, returns rows of type row_type
with multiplicity row_mult
, and which sends a query string based on a preliminary form given by f di
, where di
is the Caqti_driver_info.t
of the target driver. The preliminary query string may contain parameter and static references as described in the introduction of this section.
exec_p ?env ?oneshot arg_type s
is a shortcut for create_p ?env ?oneshot
arg_type Caqti_type.unit Caqti_mult.zero (fun _ -> s)
.
find_p ?env ?oneshot arg_type row_type s
is a shortcut for create_p ?env ?oneshot arg_type row_type Caqti_mult.one (fun _ -> s)
.
find_opt_p arg_type ?env ?oneshot row_type s
is a shortcut for create_p
?env ?oneshot arg_type row_type Caqti_mult.zero_or_one (fun _ -> s)
.
collect_p arg_type ?env ?oneshot row_type s
is a shortcut for create_p arg_type ?env ?oneshot row_type Caqti_mult.many (fun _ -> s)
.
Printing
pp ppf req
prints req
on ppf
in a form suitable for human inspection.
pp_with_param ppf (req, param)
prints req
and the associated param
to ppf
. This functions is meant for debugging; the output is neither guaranteed to be consistent across releases nor to contain a complete record of the data.
Due to concerns about exposure of sensitive data in debug logs, this function reverts to pp
unless the environment varibale CAQTI_DEBUG_PARAM
is set to true
. If you enable it for applications which do not consistenly annotate sensitive parameters with Caqti_type.redacted
, make sure your debug logs are well secured.
How to Dynamically Assemble Queries and Parameters
In some cases, queries are constructed dynamically, e.g. when translating an expression for searching a database into SQL. In such cases the number of parameters and their types will typically vary, as well. A helper like the following can be used to existentially pack the parameter types along with the corresponding parameter values to allow collecing them incrementally:
module Dynparam = struct
type t = Pack : 'a Caqti_type.t * 'a -> t
let empty = Pack (Caqti_type.unit, ())
let add t x (Pack (t', x')) = Pack (Caqti_type.tup2 t' t, (x', x))
end
Now, given a param : Dynparam.t
and a corresponding query string qs
, one can construct a request and execute it:
let Dynparam.Pack (pt, pv) = param in
let req = Caqti_request.exec ~oneshot:true pt qs in
C.exec req pv
Note that dynamically constructed requests should have ~oneshot:true
unless they are memoized. Also note that it is natural to use create
for dynamically constructed queries, since it accepts the easily composible Caqti_query.t
type instead of plain strings.
This scheme can be specialized for particular use cases, including generation of fragments of the query
, which reduces the risk of wrongly matching up parameters with their uses in the query string.