!HS      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQR None}e  !"#$%&'(,+*).-/01:98765432=<;>?@ABCFEDGHIJNMLKTSRQPOhgfedcba`_^]\[ZYXWVUkjinmlopqrstuwvx|{zy~}     $#"! +*)('&%;:9876543210/.-,GFEDCBA@?>=<PONMLKJIHSRQUT\[ZYXWVcba`_^] None&',/2=>?@ACHSVXhd esqueleto1(Internal) Class for mapping results coming from  into actual results.This looks very similar to RawSqle, and it is! However, there are some crucial differences and ultimately they're different classes.e esqueleto!Creates the variable part of the SELECT query and returns the list of ;s that will be given to (.f esqueleto(Number of columns that will be consumed.g esqueleto1Transform a row of the result into the data type.h esqueletoCreate  INSERT INTO clause instead.i esqueleto,(Internal) Mode of query being converted by .S esqueletoPhantom type used to mark a  INSERT INTO query.s esqueleto!An expression on the SQL backend.There are many comments describing the constructors of this data type. However, Haddock doesn't like GADTs, so you'll have to read them by hitting "Source". esqueleto1Information needed to escape and use identifiers. esqueletoHList of identifiers already in use and supply of temporary identifiers.T esqueleto Identifier used for table names.U esqueletoA locking clause.V esqueletoA LIMIT clause. esqueletoA ORDER BY clause.W esqueletoA HAVING cause.X esqueletoA GROUP BY clause.Y esqueleto A complete WHERE clause.Z esqueleto A part of a SET clause.[ esqueleto A part of a FROM clause.\ esqueletoThe DISTINCT "clause".] esqueletoThe default, everything.^ esqueletoOnly DISTINCT, SQL standard._ esqueleto DISTINCT ON, PostgreSQL extension.` esqueletoSide data written by . esqueletoConstraint synonym for  persistent entities whose backend is >. esqueletoSQL backend for  esqueleto using >.a esqueletoException data type for  esqueleto internal errors esqueleto%(Internal) Class that implements the JOIN  magic (see b). esqueleto+(Internal) Class that implements the tuple  magic (see b). esqueletoClass that enables one to use : to convert an entity's key on a query into another (cf. ). esqueletoPhantom class of data types that are treated as strings by the RDBMS. It has no methods because it's only used to avoid type errors such as trying to concatenate integers."If you have a custom data type or newtype2, feel free to make it an instance of this class. Since: 2.4.0 esqueleto0Different kinds of locking clauses supported by .iNote that each RDBMS has different locking support. The constructors of this datatype specify only the syntax$ of the locking mechanism, not its  semantics?. For example, even though both MySQL and PostgreSQL support :, there are no guarantees that they will behave the same. Since: 2.2.7 esqueleto FOR UPDATE5 syntax. Supported by MySQL, Oracle and PostgreSQL. Since: 2.2.7 esqueletoFOR UPDATE SKIP LOCKED5 syntax. Supported by MySQL, Oracle and PostgreSQL. Since: 2.2.7 esqueleto FOR SHARE" syntax. Supported by PostgreSQL. Since: 2.2.7 esqueletoLOCK IN SHARE MODE syntax. Supported by MySQL. Since: 2.2.7 esqueletoPhantom type used by ". esqueletoPhantom type for a SET0 operation on an entity of the given type (see  and '(=.)'). esqueletoPhantom type used by  and . esqueletoPhantom type used by ,  and . esqueleto((Internal) Phantom type used to process  (see b). esqueletoException thrown whenever  is used to create an ON clause but no matching JOIN is found. esqueletoE(Internal) Functions that operate on types (that should be) of kind . esqueleto (Internal)  smartJoin a b is a JOIN of the correct kind. esqueleto(Internal) Reify a JoinKind from a JOIN . This function is non-strict. esqueleto(Internal) A kind of JOIN. esqueleto  INNER JOIN esqueleto  CROSS JOIN esqueleto LEFT OUTER JOIN esqueleto RIGHT OUTER JOIN esqueleto FULL OUTER JOIN esqueletoData type that represents a FULL OUTER JOIN (see  for an example). esqueletoData type that represents a RIGHT OUTER JOIN (see  for an example). esqueletoData type that represents a LEFT OUTER JOIN. For example,  select $  $ \(person `` pet) -> ... is translated into /SELECT ... FROM Person LEFT OUTER JOIN Pet ...  See also: . esqueletoData type that represents a  CROSS JOIN (see  for an example). esqueletoData type that represents an  INNER JOIN (see  for an example).c esqueleto@A class for constructors or function which result type is known. esqueletouA class of things that can be converted into a list of SomeValue. It has instances for tuples and is the reason why  can take tuples, like  (foo  FooId, foo  FooName, foo  FooType). esqueletoA wrapper type for for any expr (Value a) for all a. esqueletohA list of single values. There's a limited set of functions able to work with this data type (such as , ,  and ). esqueleto=A single value (as opposed to a whole entity). You may use () or () to get a  from an .b esqueleto(Internal) Start a  query with an entity.  does two kinds of magic using b, d and e: >The simple but tedious magic of allowing tuples to be used.$The more advanced magic of creating JOIN s. The JOINB is processed from right to left. The rightmost entity of the JOIN is created with b . Each JOIN( step is then translated into a call to d. In the end, e! is called to materialize the JOIN.f esqueleto(Internal) Same as b, but entity may be missing.d esqueleto(Internal) Do a JOIN.e esqueleto(Internal) Finish a JOIN. esqueletoWHERE% clause: restrict the query's result. esqueletoON clause: restrict the a JOIN's result. The ON clause will be applied to the last JOIN that does not have an ON clause yet. If there are no JOIN s without ON+ clauses (either because you didn't do any JOIN, or because all JOINs already have their own ON clauses), a runtime exception  is thrown. ON! clauses are optional when doing JOINs.%On the simple case of doing just one JOIN , for example  select $  $ \(foo `` bar) -> do  (foo  FooId  bar  BarFooId) ... Pthere's no ambiguity and the rules above just mean that you're allowed to call ; only once (as in SQL). If you have many joins, then the s are applied on the reverse order that the JOINs appear. For example:  select $  $ \(foo `` bar `` baz) -> do  (baz  BazId  bar  BarBazId)  (foo  FooId  bar  BarFooId) ...  The order is reversed; in order to improve composability. For example, consider query1 and query2 below: let query1 =  $ \(foo `` bar) -> do  (foo  FooId  bar  BarFooId) query2 =  $ \(mbaz `#` quux) -> do return (mbaz f BazName, quux) test1 = (,) <$> query1 <*> query2 test2 = flip (,) <$> query2 <*> query1 If the order was not reversed, then test2 would be broken: query1's  would refer to query2's . esqueletoGROUP BY6 clause. You can enclose multiple columns in a tuple.  select $  \(foo `` bar) -> do  (foo  FooBarId  bar  BarId)  (bar  BarId, bar  BarName) return (bar  BarId, bar  BarName, countRows) DWith groupBy you can sort by aggregate functions, like so (we used let to restrict the more general  to SqlSqlExpr (Value Int)) to avoid ambiguity---the second use of  has its type restricted by the :: Int below): r <- select $  \(foo `` bar) -> do  (foo  FooBarId  bar  BarId)  $ bar  BarName let countRows' =   [ countRows'] return (bar " BarName, countRows') forM_ r $ \( name, 2 count) -> do print name print (count :: Int)  esqueletoORDER BY clause. See also  and .Multiple calls to 1 get concatenated on the final query, including . esqueleto/Ascending order of this field or SqlExpression. esqueleto0Descending order of this field or SqlExpression. esqueletoLIMIT%. Limit the number of returned rows. esqueletoOFFSET. Usually used with . esqueletoDISTINCT. Change the current SELECT into SELECT DISTINCT. For example: select $ distinct $  \foo -> do ... (Note that this also has the same effect:  select $ ) \foo -> do distinct (return ()) ...  Since: 2.2.4 esqueleto DISTINCT ON. Change the current SELECT into #SELECT DISTINCT ON (SqlExpressions). For example:  select $  \foo ->  [ (foo ^. FooName),  (foo ^. FooState)] $ do ... &You can also chain different calls to . The above is equivalent to:  select $  \foo ->  [ (foo ^. FooName)] $  [ (foo ^. FooState)] $ do ...  Each call to & adds more SqlExpressions. Calls to  override any calls to .4Note that PostgreSQL requires the SqlExpressions on  DISTINCT ON% to be the first ones to appear on a ORDER BYi. This is not managed automatically by esqueleto, keeping its spirit of trying to be close to raw SQL.Supported by PostgreSQL only. Since: 2.2.4 esqueletoCErase an SqlExpression's type so that it's suitable to be used by . Since: 2.2.4 esqueleto'A convenience function that calls both  and . In other words, + [asc foo, desc bar, desc quux] $ do ... is the same as: ' [don foo, don bar, don quux] $ do ' [asc foo, desc bar, desc quux] ...  Since: 2.2.4 esqueletoORDER BY random() clause. Since: 1.3.10 esqueletoHAVING. Since: 1.2.2 esqueleto1Add a locking clause to the query. Please read % documentation and your RDBMS manual.If multiple calls to 3 are made on the same query, the last one is used. Since: 2.2.7 esqueletoExecute a subquery SELECTO in an SqlExpression. Returns a simple value so should be used only when the SELECT- query is guaranteed to return just one row. esqueletoProject a field of an entity. esqueletoGProject an SqlExpression that may be null, guarding against null cases. esqueleto.Project a field of an entity that may be null. esqueleto5Lift a constant value from Haskell-land to the query. esqueletoIS NULL comparison. esqueleto Analogous to g, promotes a value of type typ into one of type  Maybe typ. It should hold that  . Just === just . . esqueletoNULL value. esqueleto Join nested hs in a O into one. This is useful when calling aggregate functions on nullable fields. esqueletoCOUNT(*) value. esqueletoCOUNT. esqueletoCOUNT(DISTINCT x). Since: 2.4.1 esqueletoBETWEEN. @since: 3.1.0 esqueletoAllow a number of one type to be used as one of another type via an implicit cast. An explicit cast is not made, this function changes only the types on the Haskell side.Caveat: Trying to use castNum from Double to IntZ will not result in an integer, the original fractional number will still be used! Use ,  or  instead.Safety+: This operation is mostly safe due to the i constraint between the types and the fact that RDBMSs usually allow numbers of different types to be used interchangeably. However, there may still be issues with the query not being accepted by the RDBMS or  persistent not being able to parse it. Since: 2.2.9 esqueletoSame as , but for nullable values. Since: 2.2.9 esqueletoCOALESCE function. Evaluates the arguments in order and returns the value of the first non-NULL SqlExpression, or NULL (Nothing) otherwise. Some RDBMSs (such as SQLite) require at least two arguments; please refer to the appropriate documentation. Since: 1.4.3 esqueletoLike coalesce{, but takes a non-nullable SqlExpression placed at the end of the SqlExpression list, which guarantees a non-NULL result. Since: 1.4.3 esqueletoLOWER function. esqueletoLIKE operator. esqueletoILIKE operator (case-insensitive LIKE).Supported by PostgreSQL only. Since: 2.2.3 esqueleto The string . May be useful while using  and concatenation ( or a, depending on your database). Note that you always have to type the parenthesis, for example: name ` ` (%) ++.  "John" ++. (%)  esqueletoThe CONCATT function with a variable number of parameters. Supported by MySQL and PostgreSQL. esqueletoThe ||7 string concatenation operator (named after Haskell's j% in order to avoid naming clash with '). Supported by SQLite and PostgreSQL. esqueletoCast a string type into Text4. This function is very useful if you want to use newtype.s, or if you want to apply functions such as  to strings of different types.Safety:[ This is a slightly unsafe function, especially if you have defined your own instances of . Also, since h is an instance of k, it's possible to turn a nullable value into a non-nullable one. Avoid using this function if possible. esqueletoExecute a subquery SELECT1 in an SqlExpression. Returns a list of values. esqueleto=Lift a list of constant value from Haskell-land to the query. esqueletoSame as  but for D. Most of the time you won't need it, though, because you can use  from inside  or g from inside . Since: 2.2.12 esqueletoIN1 operator. For example if you want to select all Persons by a list of IDs: ,SELECT * FROM Person WHERE Person.id IN (?) In  esqueleto', we may write the same query above as:  select $  $ \person -> do  $ person  PersonId ``  personIds return person Where  personIds is of type  [Key Person]. esqueletoNOT IN operator. esqueletoEXISTS operator. For example:  select $  $ \person -> do  $  $  $ \post -> do  (post  BlogPostAuthorId  person  PersonId) return person  esqueleto NOT EXISTS operator. esqueletoSET clause used on UPDATEEs. Note that while it's not a type error to use this function on a SELECT4, it will most certainly result in a runtime error. esqueletoApply a  constructor to  SqlExpr Value arguments. esqueleto Apply extra  SqlExpr Value arguments to a  constructor esqueletoCASE statement. For example: select $ return $  [  ( $  $ \p -> do  (p  PersonName   "Mike"))  ( $ , $ \v -> do let sub =  $ \c -> do  (c  PersonName  " "Mike") return (c  PersonFavNum)  (v  PersonFavNum >.  sub) return $  (v  PersonName) +.  (1 :: Int)) ] ( $  (-1)) LThis query is a bit complicated, but basically it checks if a person named "Mike"x exists, and if that person does, run the subquery to find out how many people have a ranking (by Fav Num) higher than "Mike".NOTE:9 There are a few things to be aware about this statement.fThis only implements the full CASE statement, it does not implement the "simple" CASE statement. At least one  and 4 is mandatory otherwise it will emit an error.The C is also mandatory, unlike the SQL statement in which if the ELSE is omitted it will return a NULL#. You can reproduce this via . Since: 2.1.2 esqueleto.Convert an entity's key into another entity's.8This function is to be used when you change an entity's Id- to be that of another entity. For example: <Bar barNum Int Foo bar BarId fooNum Int Primary bar For this example, declare: Pinstance ToBaseId Foo where type BaseEnt Foo = Bar toBaseIdWitness = FooKey )Now you're able to write queries such as:  $  $ (bar ` ` foo) -> do  ( (foo  FooId)  bar  BarId) return (bar, foo) ^Note: this function may be unsafe to use in conditions not like the one of the example above. Since: 2.4.3 esqueletoSyntax sugar for . Since: 2.1.2 esqueletoSyntax sugar for . Since: 2.1.2 esqueletoSyntax sugar for . Since: 2.1.2k esqueletoConvert a constructor for a  key on a record to the  that defines it. You can supply just the constructor itself, or a value of the type - the library is capable of figuring it out from there.l esqueletoARender updates to be use in a SET clause for a given sql backend. esqueletoFROM# clause: bring entities into scope.This function internally uses two type classes in order to provide some flexibility of how you may call it. Internally we refer to these type classes as the two different magics.&The innermost magic allows you to use from with the following types:expr (Entity val),, which brings a single entity into scope.expr (Maybe (Entity val))-, which brings a single entity that may be NULL into scope. Used for  OUTER JOINs.A JOINB of any other two types allowed by the innermost magic, where a JOIN may be an , a , a , a , or a . The JOINs have left fixity.&The outermost magic allows you to use fromn on any tuples of types supported by innermost magic (and also tuples of tuples, and so on), up to 8-tuples.Note that using fromz for the same entity twice does work and corresponds to a self-join. You don't even need to use two different calls to from, you may use a JOIN or a tuple.,The following are valid examples of uses of fromH (the types of the arguments of the lambda are inside square brackets):  $ \person -> ...  $ \(person, blogPost) -> ...  $ \(p ` ` mb) -> ...  $ \(p1 `` f ` ` p2) -> ...  $ \((p1 `` f) ` ` p2) -> ... CThe types of the arguments to the lambdas above are, respectively: person :: ( Esqueleto query expr backend , PersistEntity Person , PersistEntityBackend Person ~ backend ) => expr (Entity Person) (person, blogPost) :: (...) => (expr (Entity Person), expr (Entity BlogPost)) (p `[` mb) :: (...) => InnerJoin (expr (Entity Person)) (expr (Maybe (Entity BlogPost))) (p1 `` f `` p2) :: (...) => InnerJoin (InnerJoin (expr (Entity Person)) (expr (Entity Follow))) (expr (Entity Person)) (p1 `` (f `` p2)) :: :: (...) => InnerJoin (expr (Entity Person)) (InnerJoin (expr (Entity Follow)) (expr (Entity Person))) 5Note that some backends may not support all kinds of JOINs.m esqueletoCollect ns on o!s. Returns the first unmatched n*s data on error. Returns a list without  OnClauses on success.p esqueletoCreate a fresh T. If possible, use the given .q esqueletoUse an identifier. esqueleto#(Internal) Create a case statement. Since: 2.1.1 esqueleto1(Internal) Create a custom binary operator. You should not use this function directly since its type is very general, you should always use it with an explicit type signature. For example: e(==.) :: SqlExpr (Value a) -> SqlExpr (Value a) -> SqlExpr (Value Bool) (==.) = unsafeSqlBinOp " = " zIn the example above, we constraint the arguments to be of the same type and constraint the result to be a boolean value. esqueleto Similar to , but may also be applied to composite keys. Uses the operator given as the second argument whenever applied to composite keys.Usage example: v(==.) :: SqlExpr (Value a) -> SqlExpr (Value a) -> SqlExpr (Value Bool) (==.) = unsafeSqlBinOpComposite " = " " AND " <Persistent has a hack for implementing composite keys (see wU doc for more details), so we're forced to use a hack here as well. We deconstruct v values based on two rules:HIf it is a single placeholder, then it's assumed to be coming from a 0Y and thus its components are separated so that they may be applied to a composite key.If it is not a single placeholder, then it's assumed to be a foreign (composite or not) key, so we enforce that it has no placeholders and split it on the commas.  esqueleto4(Internal) A raw SQL value. The same warning from " applies to this function as well.  esqueletoC(Internal) A raw SQL function. Once again, the same warning from " applies to this function as well.  esqueletoc(Internal) An unsafe SQL function to extract a subfield from a compound field, e.g. datetime. See  for warnings. Since: 1.3.6.r esqueletoL(Internal) A raw SQL function. Preserves parentheses around arguments. See  for warnings.  esqueletoE(Internal) An explicit SQL type cast using CAST(value as type). See  for warnings.  esqueleto_(Internal) Coerce a value's type from 'SqlExpr (Value a)' to 'SqlExpr (Value b)'. You should not6 use this function unless you know what you're doing! esqueletow(Internal) Coerce a value's type from 'SqlExpr (ValueList a)' to 'SqlExpr (Value a)'. Does not work with empty lists. esqueleto(Internal) Execute an  esqueleto SELECT  inside  persistent's > monad. esqueleto Execute an  esqueleto SELECT query inside  persistent's > monad and return a s of rows. esqueleto Execute an  esqueleto SELECT query inside  persistent's >! monad and return a list of rows.We've seen that M has some magic about which kinds of things you may bring into scope. This f function also has some magic for which kinds of things you may bring back to Haskell-land by using SqlQuery's return:You may return a  SqlExpr ( v) for an entity v (i.e., like the *; in SQL), which is then returned to Haskell-land as just Entity v.You may return a SqlExpr (Maybe (Entity v)) for an entity v that may be NULL., which is then returned to Haskell-land as Maybe (Entity v) . Used for  OUTER JOINs.You may return a  SqlExpr ( t) for a value t" (i.e., a single column), where t is any instance of ., which is then returned to Haskell-land as Value t. You may use Value to return projections of an Entity (see () and ()@) or to return any other value calculated on the query (e.g.,  or ).The  SqlSelect a rR class has functional dependencies that allow type information to flow both from a to r] and vice-versa. This means that you'll almost never have to give any type signatures for  esqueleto# queries. For example, the query  $ from $ \p -> return p+ alone is ambiguous, but in the context of  do ps <-  $ T $ \p -> return p liftIO $ mapM_ (putStrLn . personName . entityVal) ps &we are able to infer from that single personName . entityVal function composition that the p inside the query is of type SqlExpr (Entity Person). esqueleto(Internal) Run a s of rows. esqueleto(Internal) Execute an  esqueleto statement inside  persistent's > monad. esqueleto Execute an  esqueleto DELETE query inside  persistent's >b monad. Note that currently there are no type checks for statements that should not appear on a DELETE query.Example of usage:  $  $ \appointment ->  (appointment  AppointmentDate   now) Unlike !, there is a useful way of using Q that will lead to type ambiguities. If you want to delete all rows (i.e., no . clause), you'll have to use a type signature:  $  $ \(appointment :: s ( Appointment)) -> return ()  esqueletoSame as *, but returns the number of rows affected. esqueleto Execute an  esqueleto UPDATE query inside  persistent's >b monad. Note that currently there are no type checks for statements that should not appear on a UPDATE query.Example of usage:  $ \p -> do  p [ PersonAge   ( thisYear) -. p  PersonBorn ]  $ isNothing (p  PersonAge)  esqueletoSame as *, but returns the number of rows affected. esqueleto(Internal) Pretty prints a  into a SQL query.@Note: if you're curious about the SQL query being generated by  esqueletoT, instead of manually using this function (which is possible but tedious), see the  function (along with , , etc). esqueleto Renders a  into a Text value along with the list of ;-s that would be supplied to the database for ? placeholders.You must ensure that the i8 you pass to this function corresponds with the actual @. If you pass a query that uses incompatible features (like an INSERT statement with a SELECT' mode) then you'll get a weird result. esqueleto Renders a  into a Text value along with the list of ;-s that would be supplied to the database for ? placeholders.You must ensure that the i8 you pass to this function corresponds with the actual @. If you pass a query that uses incompatible features (like an INSERT statement with a SELECT' mode) then you'll get a weird result. esqueleto Renders a  into a Text value along with the list of ;-s that would be supplied to the database for ? placeholders.You must ensure that the i8 you pass to this function corresponds with the actual @. If you pass a query that uses incompatible features (like an INSERT statement with a SELECT' mode) then you'll get a weird result. esqueleto Renders a  into a Text value along with the list of ;-s that would be supplied to the database for ? placeholders.You must ensure that the i8 you pass to this function corresponds with the actual @. If you pass a query that uses incompatible features (like an INSERT statement with a SELECT' mode) then you'll get a weird result. esqueleto Renders a  into a Text value along with the list of ;-s that would be supplied to the database for ? placeholders.You must ensure that the i8 you pass to this function corresponds with the actual @. If you pass a query that uses incompatible features (like an INSERT statement with a SELECT' mode) then you'll get a weird result.t esqueletoMaterialize a SqlExpr (Value a)." esqueleto Insert a  for every selected value. Since: 2.4.2# esqueleto Insert a 5 for every selected value, return the count afterwardu esqueleto Since: 1.4.4v esqueleto Since: 2.4.0w esqueleto Since: 2.3.0x esqueleto Since: 2.3.0y esqueleto Since: 2.3.0z esqueleto Since: 2.3.0{ esqueleto Since: 2.3.0| esqueletoEYou may return tuples (up to 16-tuples) and tuples of tuples from a  query.} esqueleto?You may return any single value (i.e. a single column) from a  query.~ esqueletoYou may return a possibly-NULL  from a  query. esqueletoYou may return an  from a  query. esqueletoNot useful for , but used for  and . esqueleto INSERT INTO hack. esqueletoWhether to render as an j, k, etc. esqueleto!The SQL query you want to render. esqueleto!The SQL query you want to render. esqueleto!The SQL query you want to render. esqueleto!The SQL query you want to render. esqueleto!The SQL query you want to render.GdfehgimljknopqrSs}yxvw{|zu~tTUVWXYZ[no\]^_`acbfdeklmpq   r   !t"#22222222229 44444432667722533333None&'2=>?@ACHV|None&',/2=>?@ACHSVXbAdghefikjlmnoprqst~uz|{wvxy}      !"#Ast~uz|{wvxy}"#    nikjlmprqdghef  !oNone&'=>?SX$ esqueleto valkey i =  .  ( 2https://github.com/prowdsponsor/esqueleto/issues/9).% esqueletovalJ is like val% but for something that is already a Value0. The use case it was written for was, given a Value lift the Key for that Valueu into the query expression in a type safe way. However, the implementation is more generic than that so we call it valJ.Its important to note that the input entity and the output entity are constrained to be the same by the type signature on the function ( 1https://github.com/prowdsponsor/esqueleto/pull/69). Since: 1.4.2& esqueleto Synonym for   that does not clash with  esqueleto's .' esqueleto:Avoid N+1 queries and join entities into a map structure  getFoosAndNestedBarsFromParent :: ParentId -> (Map (Key Foo) (Foo, [Maybe (Entity Bar)])) getFoosAndNestedBarsFromParent parentId =  associateJoin $  $  $ \(foo `` bar) -> do  (bar  BarFooId  foo  FooId)  (foo  FooParentId   parentId)  (foo, bar)   Since: 3.1.2  !"#$%&'(,+*).-/01:98765432=<;>?@ABCFEDGHIJNMLKTSRQPOhgfedcba`_^]\[ZYXWVUkjinmlopqrstuwvx|{zy~}     $#"! +*)('&%;:9876543210/.-,GFEDCBA@?>=<PONMLKJIHSRQUT\[ZYXWVcba`_^]s"#$%&'s"#$%'&/x10   $&%('#! "GHIutwvcba`_^]|{zy~}.-,+*)A:98765432CB=<;FED@?>NMLKsJhgfedcba`_^]\[ZYXWVUopkjiqnmlrTSRQPO     $#"! UT+*)('&%PONMLKJIH\[ZYXWV;:9876543210/.-,GFEDCBA@?>=<SRQNone( esqueleto(random()H) Split out into database specific modules because MySQL uses `rand()`. Since: 2.6.0((None &'>SXW) esqueletoAggregate mode* esqueletoALL+ esqueletoDISTINCT, esqueleto(random()H) Split out into database specific modules because MySQL uses `rand()`. Since: 2.6.0 esqueletoEmpty array literal. (val []) does unfortunately not work- esqueleto-Coalesce an array with an empty default value. esqueletoB(Internal) Create a custom aggregate functions with aggregate modeDo notT use this function directly, instead define a new function and give it a type (see )1 esqueleto( array_agg/) Concatenate distinct input values, including NULLs, into an array. Since: 2.5.32 esqueleto( array_remove?) Remove all elements equal to the given value from the array. Since: 2.5.33 esqueletoRemove NULL values from an array4 esqueleto( string_agg5) Concatenate input values separated by a delimiter.5 esqueleto( string_agg5) Concatenate input values separated by a delimiter. Since: 2.2.86 esqueleto(chrs) Translate the given integer to a character. (Note the result will depend on the character set of your database.) Since: 2.2.11: esqueleto7Inserts into a table the results of a query similar to "J but allows to update values that violate a constraint during insertions.Example of usage: share [ mkPersist sqlSettings , mkDeleteCascade sqlSettings , mkMigrate "migrate" ] [persistLowerCase| Bar num Int deriving Eq Show Foo num Int UniqueFoo num deriving Eq Show |] insertSelectWithConflict UniqueFoo -- (UniqueFoo undefined) or (UniqueFoo anyNumber) would also work (from $ b -> return $ Foo <# (b ^. BarNum) ) (current excluded -> [FooNum =. (current ^. FooNum) +. (excluded ^. FooNum)] ) Inserts to table Foo all Bar.num values and in case of conflict SomeFooUnique, the conflicting value is updated to the current plus the excluded.; esqueletoSame as :) but returns the number of rows affected.4 esqueleto Aggregate mode (ALL or DISTINCT) esqueleto Input values. esqueleto Delimiter. esqueletoORDER BY clauses esqueletoConcatenation.5 esqueleto Input values. esqueleto Delimiter. esqueletoConcatenation.8 esqueletonew record to insert esqueleto/updates to perform if the record already exists esqueleto.the record in the database after the operation9 esqueleto uniqueness constraint to find by esqueletonew record to insert esqueleto/updates to perform if the record already exists esqueleto.the record in the database after the operation: esqueletoUnique constructor or a unique, this is used just to get the name of the postgres constraint, the value(s) is(are) never used, so if you have a unique "MyUnique 0", "MyUnique undefined" would work as well. esqueleto Insert query. esqueletoA list of updates to be applied in case of the constraint being violated. The expression takes the current and excluded value to produce the updates.)*+,-./0123456789:;)*+10/2354-67,89:;. None4567M)@= esqueleto!Used with certain JSON operators.This data type has i and A instances for ease of use by using integer and string literals.3 :: JSONAccessor JSONIndex 3-3 :: JSONAccessor JSONIndex -3"name" :: JSONAccessorJSONKey "name"NOTE: DO NOT USE ANY OF THE i METHODS ON THIS TYPE!@ esqueletos of a NULL-able A value. Hence the h.1Note: NULL here is a PostgreSQL NULL, not a JSON A esqueleto;Newtype wrapper around any type with a JSON representation.D esqueleto5Convenience function to lift a regular value into a A expression. esqueletojsonb esqueleto esqueleto+I repeat, DO NOT use any method other than ! esqueletoODatabase type(s), should appear different from Haskell name, e.g. "integer" or INT, not Int. esqueletoIncorrect value esqueleto Error message esqueletoReceived value esqueletoAdditional error esqueleto Error message =?>@ABCDNone E esqueleto"Requires PostgreSQL version >= 9.3eThis function extracts the jsonb value from a JSON array or object, depending on whether you use an int or a text. (cf. =)As long as the left operand is jsonb>, this function will not throw an exception, but will return NULL when an int4 is used on anything other than a JSON array, or a text/ is used on anything other than a JSON object.PostgreSQL Documentation  | Type | Description | Example | Example Result ----+------+--------------------------------------------+--------------------------------------------------+---------------- -> | int | Get JSON array element (indexed from zero) | '[{"a":"foo"},{"b":"bar"},{"c":"baz"}]'::json->2 | {"c":"baz"} -> | text | Get JSON object field by key | '{"a": {"b":"foo"}} '::json->'a' | {"b":"foo"} F esqueleto"Requires PostgreSQL version >= 9.3 Identical to E!, but the resulting DB type is a text2, so it could be chained with anything that uses text.$CAUTION: if the "scalar" JSON value null is the result 3of this function, PostgreSQL will interpret it as a  PostgreSQL NULL value, and will therefore be  instead of (Just "null")PostgreSQL Documentation E | Type | Description | Example | Example Result -----+------+--------------------------------+-----------------------------+---------------- ->> | int | Get JSON array element as text | '[1,2,3]'::json->>2 | 3 ->> | text | Get JSON object field as text | '{"a":1,"b":2} '::json->>'b' | 2 G esqueleto"Requires PostgreSQL version >= 9.3This operator can be used to select a JSON value from deep inside another one. It only works on objects and arrays and will result in NULL ()) when encountering any other JSON type.The s used in the right operand list will always select an object field, but can also select an index from a JSON array if that text is parsable as an integer.Consider the following: x ^. TestBody #>. ["0","1"] !The following JSON values in the test table's body column will be affected:  Values in column | Resulting value --------------------------------------+---------------------------- {"0":{"1":"Got it!"}} | "Got it!" {"0":[null,["Got it!","Even here!"]]} | ["Got it!", "Even here!"] [{"1":"Got it again!"}] | "Got it again!" [[null,{"Wow":"so deep!"}]] | {"Wow": "so deep!"} false | NULL "nope" | NULL 3.14 | NULL PostgreSQL Documentation / | Type | Description | Example | Example Result -----+--------+-----------------------------------+--------------------------------------------+---------------- #> | text[] | Get JSON object at specified path | '{"a": {"b":{"c": "foo"}}} '::json#>'{a,b}' | {"c": "foo"} H esqueleto"Requires PostgreSQL version >= 9.3This function is to G as F is to E$CAUTION: if the "scalar" JSON value null is the result 3of this function, PostgreSQL will interpret it as a  PostgreSQL NULL value, and will therefore be  instead of (Just "null")PostgreSQL Documentation I | Type | Description | Example | Example Result -----+--------+-------------------------------------------+---------------------------------------------+---------------- #>> | text[] | Get JSON object at specified path as text | '{"a":[1,2,3],"b":[4,5,6]} '::json#>>' {a,2}' | 3 I esqueleto"Requires PostgreSQL version >= 9.4cThis operator checks for the JSON value on the right to be a subset of the JSON value on the left.dExamples of the usage of this operator can be found in the Database.Persist.Postgresql.JSON module.(here:  khttps://hackage.haskell.org/package/persistent-postgresql-2.10.0/docs/Database-Persist-Postgresql-JSON.html)PostgreSQL Documentation F | Type | Description | Example ----+-------+-------------------------------------------------------------+--------------------------------------------- @> | jsonb | Does the left JSON value contain within it the right value? | '{"a":1, "b":2}'::jsonb @> '{"b":2}'::jsonb J esqueleto"Requires PostgreSQL version >= 9.4 This operator works the same as Iz, just with the arguments flipped. So it checks for the JSON value on the left to be a subset of JSON value on the right.dExamples of the usage of this operator can be found in the Database.Persist.Postgresql.JSON module.(here:  khttps://hackage.haskell.org/package/persistent-postgresql-2.10.0/docs/Database-Persist-Postgresql-JSON.html)PostgreSQL Documentation = | Type | Description | Example ----+-------+----------------------------------------------------------+--------------------------------------------- <@ | jsonb | Is the left JSON value contained within the right value? | '{"b":2}'::jsonb <@ '{"a":1, "b":2}'::jsonb K esqueleto"Requires PostgreSQL version >= 9.4This operator checks if the given text is a top-level member of the JSON value on the left. This means a top-level field in an object, a top-level string in an array or just a string value.dExamples of the usage of this operator can be found in the Database.Persist.Postgresql.JSON module.(here:  khttps://hackage.haskell.org/package/persistent-postgresql-2.10.0/docs/Database-Persist-Postgresql-JSON.html)PostgreSQL Documentation , | Type | Description | Example ---+------+-----------------------------------------------------------------+------------------------------- ? | text | Does the string exist as a top-level key within the JSON value? | '{"a":1, "b":2}'::jsonb ? b L esqueleto"Requires PostgreSQL version >= 9.4This operator checks if ANY of the given texts is a top-level member of the JSON value on the left. This means any top-level field in an object, any top-level string in an array or just a string value.dExamples of the usage of this operator can be found in the Database.Persist.Postgresql.JSON module.(here:  khttps://hackage.haskell.org/package/persistent-postgresql-2.10.0/docs/Database-Persist-Postgresql-JSON.html)PostgreSQL Documentation < | Type | Description | Example ----+--------+--------------------------------------------------------+--------------------------------------------------- ?| | text[] | Do any of these array strings exist as top-level keys? | '{"a":1, "b":2, "c":3}'::jsonb ?| array[b, c] M esqueleto"Requires PostgreSQL version >= 9.4This operator checks if ALL of the given texts are top-level members of the JSON value on the left. This means a top-level field in an object, a top-level string in an array or just a string value.dExamples of the usage of this operator can be found in the Database.Persist.Postgresql.JSON module.(here:  khttps://hackage.haskell.org/package/persistent-postgresql-2.10.0/docs/Database-Persist-Postgresql-JSON.html)PostgreSQL Documentation & | Type | Description | Example ----+--------+--------------------------------------------------------+---------------------------------------- ?& | text[] | Do all of these array strings exist as top-level keys? | '["a", "b"]'::jsonb ?& array[a, b] N esqueleto"Requires PostgreSQL version >= 9.5This operator concatenates two JSON values. The behaviour is self-evident when used on two arrays, but the behaviour on different combinations of JSON values might behave unexpectedly.=CAUTION: THIS FUNCTION THROWS AN EXCEPTION WHEN CONCATENATING 'A JSON OBJECT WITH A JSON SCALAR VALUE!ArraysGThis operator is a standard concatenation function when used on arrays: \[1,2] || [2,3] == [1,2,2,3] [] || [1,2,3] == [1,2,3] [1,2,3] || [] == [1,2,3] ObjectsDWhen concatenating JSON objects with other JSON objects, the fields from the JSON object on the right are added to the JSON object on the left. When concatenating a JSON object with a JSON array, the object will be inserted into the array; either on the left or right, depending on the position relative to the operator.GWhen concatening an object with a scalar value, an exception is thrown. L{"a": 3.14} || {"b": true} == {"a": 3.14, "b": true} {"a": "b"} || {"a": null} == {"a": null} {"a": {"b": true, "c": false}} || {"a": {"b": false}} == {"a": {"b": false}} {"a": 3.14} || [1,null] == [{"a": 3.14},1,null] [1,null] || {"a": 3.14} == [1,null,{"a": 3.14}] 1 || {"a": 3.14} == ERROR: invalid concatenation of jsonb objects {"a": 3.14} || false == ERROR: invalid concatenation of jsonb objects  Scalar valuesScalar values can be thought of as being singleton arrays when used with this operator. This rule does not apply when concatenating with JSON objects. 1 || null == [1,null] true || "a" == [true,"a"] [1,2] || false == [1,2,false] null || [1,"a"] == [null,1,"a"] {"a":3.14} || true == ERROR: invalid concatenation of jsonb objects 3.14 || {"a":3.14} == ERROR: invalid concatenation of jsonb objects {"a":3.14} || [true] == [{"a":3.14},true] [false] || {"a":3.14} == [false,{"a":3.14}] PostgreSQL Documentation , | Type | Description | Example ----+-------+-----------------------------------------------------+-------------------------------------------- || | jsonb | Concatenate two jsonb values into a new jsonb value | '["a", "b"]'::jsonb || '["c", "d"]'::jsonb  Note: The ||7 operator concatenates the elements at the top level of 6each of its operands. It does not operate recursively.GFor example, if both operands are objects with a common key field name, Jthe value of the field in the result will just be the value from the right  hand operand.O esqueleto"Requires PostgreSQL version >= 9.5This operator can remove a key from an object or a string element from an array when using text, and remove certain elements by index from an array when using integers.DNegative integers delete counting from the end of the array. (e.g. -1 being the last element, -2 being the second to last, etc.)FCAUTION: THIS FUNCTION THROWS AN EXCEPTION WHEN USED ON ANYTHING OTHER FTHAN OBJECTS OR ARRAYS WHEN USING TEXT, AND ANYTHING OTHER THAN ARRAYS WHEN USING INTEGERS!Objects and arrays {"a": 3.14} - "a" == {} {"a": "b"} - "b" == {"a": "b"} {"a": 3.14} - "a" == {} {"a": 3.14, "c": true} - "a" == {"c": true} ["a", 2, "c"] - "a" == [2, "c"] -- can remove strings from arrays [true, "b", 5] - 0 == ["b", 5] [true, "b", 5] - 3 == [true, "b", 5] [true, "b", 5] - -1 == [true, "b"] [true, "b", 5] - -4 == [true, "b", 5] [] - 1 == [] {"1": true} - 1 == ERROR: cannot delete from object using integer index 1 - <anything> == ERROR: cannot delete from scalar "a" - <anything> == ERROR: cannot delete from scalar true - <anything> == ERROR: cannot delete from scalar null - <anything> == ERROR: cannot delete from scalar PostgreSQL Documentation X | Type | Description | Example ---+---------+------------------------------------------------------------------------+------------------------------------------------- - | text | Delete key/value pair or string element from left operand. | '{"a": "b"}'::jsonb - a! | | Key/value pairs are matched based on their key value. | - | integer | Delete the array element with specified index (Negative integers count | '["a", "b"]'::jsonb - 1 | | from the end). Throws an error if top level container is not an array. | P esqueleto!Requires PostgreSQL version >= 10GRemoves a set of keys from an object, or string elements from an array.(This is the same operator internally as O, but the option to use a  text array , instead of text or integerJ was only added in version 10. That's why this function is seperate from O"NOTE: The following is equivalent: ${some JSON expression} -. "a" -. "b"is equivalent to ${some JSON expression} --. ["a","b"]PostgreSQL Documentation  | Type | Description | Example ---+---------+------------------------------------------------------------------------+------------------------------------------------- - | text[] | Delete multiple key/value pairs or string elements from left operand. | '{"a": "b", "c": "d"}'::jsonb - '{a,c}'::text[] | | Key/value pairs are matched based on their key value. | Q esqueleto"Requires PostgreSQL version >= 9.56This operator can remove elements nested in an object.If a  is not parsable as a number when selecting in an array (even when halfway through the selection) an exception will be thrown.CNegative integers delete counting from the end of an array. (e.g. -1 being the last element, -2 being the second to last, etc.)4CAUTION: THIS FUNCTION THROWS AN EXCEPTION WHEN USED 2ON ANYTHING OTHER THAN OBJECTS OR ARRAYS, AND WILL 6ALSO THROW WHEN TRYING TO SELECT AN ARRAY ELEMENT WITH A NON-INTEGER TEXTObjects {"a": 3.14, "b": null} #- [] == {"a": 3.14, "b": null} {"a": 3.14, "b": null} #- ["a"] == {"b": null} {"a": 3.14, "b": null} #- ["a","b"] == {"a": 3.14, "b": null} {"a": {"b":false}, "b": null} #- ["a","b"] == {"a": {}, "b": null} Arrays rue, {"b":null}, 5] #- [] == [true, {"b":null}, 5] [true, {"b":null}, 5] #- ["0"] == [{"b":null}, 5] [true, {"b":null}, 5] #- ["b"] == ERROR: path element at position 1 is not an integer: "b" [true, {"b":null}, 5] #- ["1","b"] == [true, {}, 5] [true, {"b":null}, 5] #- ["-2","b"] == [true, {}, 5] {"a": {"b":[false,4,null]}} #- ["a","b","2"] == {"a": {"b":[false,4]}} {"a": {"b":[false,4,null]}} #- ["a","b","c"] == ERROR: path element at position 3 is not an integer: "c"  Other values 1 #- {anything} == ERROR: cannot delete from scalar "a" #- {anything} == ERROR: cannot delete from scalar true #- {anything} == ERROR: cannot delete from scalar null #- {anything} == ERROR: cannot delete from scalar PostgreSQL Documentation t | Type | Description | Example ----+--------+---------------------------------------------------------+------------------------------------ #- | text[] | Delete the field or element with specified path | '["a", {"b":1}]'::jsonb #- '{1,b}' | | (for JSON arrays, negative integers count from the end) | =>?@ABCDEFGHIJKLMNOPQABC@D=>?EFGHIJKLMOPQN E6F6G6H6I6J6K6L6M6N6O6P6Q6NoneSR esqueleto(random()H) Split out into database specific modules because MySQL uses `rand()`. Since: 2.6.0RR Safe !"#$%&'()*+,-,.,/,0,1,2,3,4,5,678797:7;7<7=>?>@>A>B>C>DEFGHGIJKJLJMJNJOJPJQJRJRJSJTJUJVJWJXJYJZJ[J\J]J]^_^`^a^b^c^d^e^f^g^h^i^j^k^k^l^m^n^o^p^q^r^s^t^u^v^w^x^y^z^{^|^}^~^~^^^^^^^^^^^        !"#$$%&'())*+,,-./01234556789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdeefghijklmlnlolplqlrls t u v w x y z { | } ~                             W                                                                                                                                                ! " # $ % & ' ()*+,-./0123456789:;<= > ? @ A B B C DEFGHIJKLMN O P Q R S T U V W X Y Z  [ \ ] ^ _ ` abcdbcebfgbhi j k l m n o p qrst u v w x y z { | } ~               V  [                                                                                             bhbhbb   bf    bc        &esqueleto-3.1.3-5qwUTDUxOvi6l4fwIpuIDuDatabase.Esqueleto$Database.Esqueleto.Internal.LanguageDatabase.Esqueleto.Internal.SqlDatabase.Esqueleto.MySQLDatabase.Esqueleto.PostgreSQL"Database.Esqueleto.PostgreSQL.JSONDatabase.Esqueleto.SQLite,Database.Esqueleto.Internal.PersistentImport$Database.Esqueleto.Internal.InternalDatabase.Persist.Storedelete,Database.Esqueleto.PostgreSQL.JSON.InstancesPaths_esqueleto(persistent-2.10.3-4Ndvho6aZz73RAyXoFoNyCDatabase.Persist.SqltransactionUndotransactionSaveDatabase.Persist.Sql.MigrationmigraterunMigrationUnsaferunMigrationSilent runMigration getMigration showMigrationprintMigrationparseMigration'parseMigration(Database.Persist.Sql.Orphan.PersistQuerydecorateSQLWithLimitOffset(Database.Persist.Sql.Orphan.PersistStore fieldDBName getFieldName tableDBName getTableName fromSqlKeytoSqlKey withRawQueryunSqlBackendKey SqlBackendKeyunSqlReadBackendKeySqlReadBackendKeyunSqlWriteBackendKeySqlWriteBackendKeyDatabase.Persist.Sql.Runclose' withSqlConn askLogFunc createSqlPool withSqlPoolliftSqlPersistMPoolrunSqlPersistMPoolrunSqlPersistM runSqlConn runSqlPoolDatabase.Persist.Sql.RawrawSql getStmtConnrawExecuteCount rawExecute rawQueryResrawQueryDatabase.Persist.Sql.ClassrawSqlProcessRowrawSqlColCountReason rawSqlColsRawSqlsqlTypePersistFieldSqlDatabase.Persist toJsonTextDatabase.Persist.Sql.Internal mkColumnsdefaultAttributeDatabase.Persist.Sql.Types cReferencecMaxLencDefaultConstraintNamecDefaultcSqlTypecNullcNameColumnCouldn'tGetSQLConnectionStatementAlreadyFinalizedPersistentSqlException SqlPersistT SqlPersistMSqlCautiousMigration MigrationConnectionPoolunSingleSingle#Database.Persist.Sql.Types.Internal readToUnknown readToWritewriteToUnknownLogFunc ISRManyKeys ISRInsertGet ISRSingleInsertSqlResult stmtQuery stmtExecute stmtReset stmtFinalize StatementconnRepsertManySql connMaxParams connLogFuncconnLimitOffset connRDBMS connNoLimitconnEscapeName connRollback connCommit connBeginconnMigrateSql connClose connStmtMapconnPutManySql connUpsertSqlconnInsertManySql connInsertSql connPrepare SqlBackendunSqlReadBackendSqlReadBackendunSqlWriteBackendSqlWriteBackendSqlBackendCanReadSqlBackendCanWriteSqlReadT SqlWriteT IsSqlBackendDatabase.Persist.Class PersistUnique PersistStore$Database.Persist.Class.DeleteCascade deleteCascade DeleteCascade#Database.Persist.Class.PersistQuery selectKeys selectKeysRes selectFirstselectSourceResPersistQueryRead deleteWhere updateWherePersistQueryWrite$Database.Persist.Class.PersistUnique checkUnique replaceUnique getByValue onlyUniqueinsertUniqueEntityinsertBygetByPersistUniqueReadputManyupsertByupsert insertUniquedeleteByPersistUniqueWrite#Database.Persist.Class.PersistStore insertRecord getEntity insertEntity belongsToJust belongsTo getJustEntitygetJust liftPersistpersistBackend BaseBackendHasPersistBackendIsPersistBackendprojectBackendBackendCompatiblePersistRecordBackendfromBackendKey toBackendKey ToBackendKey BackendKey PersistCoregetManygetPersistStoreRead updateGetreplace repsertManyrepsert insertKeyinsertEntityMany insertMany_ insertManyinsert_insertPersistStoreWrite$Database.Persist.Class.PersistEntityfromPersistValueJSONtoPersistValueJSONentityIdFromJSONentityIdToJSONkeyValueEntityFromJSONkeyValueEntityToJSON entityValues fieldLenspersistUniqueToValuespersistUniqueToFieldNamespersistUniqueKeysfromPersistValuestoPersistFieldspersistFieldDef entityDefpersistIdField keyFromValues keyToValuesUnique EntityFieldKeyPersistEntityBackend PersistEntityBackendSpecificUpdate entityVal entityKeyEntity#Database.Persist.Class.PersistFieldfromPersistValuetoPersistValue PersistFieldSomePersistFieldDatabase.Persist.Types.BasefromPersistValueTexttoEmbedEntityDefkeyAndEntityFieldsentityKeyFields entityPrimaryInactiveActive Checkmark NotNullableNullable IsNullableByNullableAttr ByMaybeAttr WhyNullableentityComments entitySum entityExtra entityDerivesentityForeigns entityUniques entityFields entityAttrsentityIdentityDB entityHaskell EntityDef ExtraLine unHaskellName HaskellNameunDBNameDBNameAttrFTListFTApp FTTypeCon FieldType fieldCommentsfieldReference fieldStrict fieldAttrs fieldSqlType fieldTypefieldDB fieldHaskellFieldDef SelfReference CompositeRefEmbedRef ForeignRef NoReference ReferenceDefembeddedFieldsembeddedHaskellEmbedEntityDef emFieldCycle emFieldEmbed emFieldDB EmbedFieldDef uniqueAttrs uniqueFields uniqueDBName uniqueHaskell UniqueDefcompositeAttrscompositeFields CompositeDefForeignFieldDefforeignNullable foreignAttrs foreignFieldsforeignConstraintNameDBNameforeignConstraintNameHaskellforeignRefTableDBNameforeignRefTableHaskell ForeignDefPersistMongoDBUnsupportedPersistMongoDBErrorPersistForeignConstraintUnmetPersistInvalidFieldPersistMarshalError PersistErrorPersistExceptionPersistDbSpecific PersistArrayPersistObjectId PersistMap PersistList PersistNullPersistUTCTimePersistTimeOfDay PersistDay PersistBoolPersistRational PersistDouble PersistInt64PersistByteString PersistText PersistValueSqlOtherSqlBlob SqlDayTimeSqlTimeSqlDaySqlBool SqlNumericSqlRealSqlInt64SqlInt32 SqlStringSqlTypeNotInInLeGeLtGtNeEq PersistFilter UpsertError KeyNotFoundUpdateExceptionOnlyUniqueExceptionDivideMultiplySubtractAddAssign PersistUpdate$Database.Persist.Class.PersistConfigrunPoolcreatePoolConfigapplyEnv loadConfigPersistConfigPoolPersistConfigBackend PersistConfig SqlSelect sqlSelectColssqlSelectColCountsqlSelectProcessRow sqlInsertIntoModeSELECTDELETEUPDATE INSERT_INTOUnsafeSqlFunctionArgument toArgList NeedParensParensNeverSqlExprEEntityEMaybeERaw ECompositeKeyEList EEmptyListEOrderBy EOrderRandom EDistinctOnESetEPreprocessedFromEInsert EInsertFinal IdentInfo IdentState OrderByClause SqlEntitySqlQueryFromPreprocessFromToBaseIdBaseEnttoBaseIdWitness LockingKind ForUpdateForUpdateSkipLockedForShareLockInShareMode InsertionUpdate DistinctOnOrderByPreprocessedFrom$OnClauseWithoutMatchingJoinException IsJoinKind smartJoin reifyJoinKindJoinKind InnerJoinKind CrossJoinKindLeftOuterJoinKindRightOuterJoinKindFullOuterJoinKind FullOuterJoinRightOuterJoin LeftOuterJoin CrossJoin InnerJoin ToSomeValues toSomeValues SomeValue ValueListValueunValuewhere_ongroupByorderByascdesclimitoffsetdistinct distinctOndondistinctOnOrderByrandhavinglocking sub_select^. withNonNull?.val isNothingjustnothingjoinV countRowscount countDistinctnot_==.>=.>.<=.<.!=.&&.||.+.-./.*.betweenrandom_round_ceiling_floor_sum_min_max_avg_castNumcastNumMcoalescecoalesceDefaultlower_likeilike%concat_++. castStringsubList_selectvalListjustListin_notInexists notExistsset=.+=.-=.*=./=.<#<&>case_toBaseIdwhen_then_else_frominitialIdentState unsafeSqlCaseunsafeSqlBinOpunsafeSqlBinOpCompositeunsafeSqlValueunsafeSqlFunctionunsafeSqlExtractSubFieldunsafeSqlCastAsveryUnsafeCoerceSqlExprValue veryUnsafeCoerceSqlExprValueListrawSelectSource selectSourceselect runSource rawEsqueleto deleteCountupdate updateCount builderToTexttoRawSqlrenderQueryToTextrenderQuerySelectrenderQueryDeleterenderQueryUpdaterenderQueryInsertInto uncommas'makeOrderByNoNewlineparens insertSelectinsertSelectCountvalkeyvalJ deleteKey associateJoinAggMode AggModeAllAggModeDistinct maybeArrayunsafeSqlAggregateFunction arrayAggWitharrayAggarrayAggDistinct arrayRemovearrayRemoveNull stringAggWith stringAggchrnow_insertSelectWithConflictinsertSelectWithConflictCount $fShowAggMode JSONAccessor JSONIndexJSONKey JSONBExprJSONBunJSONBjsonbVal->.->>.#>.#>>.@>.<@.?|.?&.--.#-. InsertFinalIdent LockingClause LimitClause HavingClause GroupByClause WhereClause SetClause FromClauseDistinctClause DistinctAllDistinctStandardSideDataEsqueletoError fromStart FinalResultfromJoin fromFinishfromStartMaybebase GHC.MaybeJustMaybeGHC.NumNumGHC.Base++ toUniqueDef renderUpdatescollectOnClausesOnClauseFromJoin newIdentForuseIdentunsafeSqlFunctionParens&conduit-1.3.1.1-DlznlOZFIihGS507pc0Ui1Data.Conduit.Internal.ConduitSourcematerializeExpr$fFunctorValue$fSqlStringMaybe$fSqlStringMarkupM$fSqlStringByteString$fSqlStringText$fSqlStringText0 $fSqlString[]$fSqlSelect(,)(,)$fSqlSelectSqlExprValue$fSqlSelectSqlExprMaybe$fSqlSelectSqlExprEntity$fSqlSelect()()$fSqlSelectSqlExprInsertFinal OrderByTypeDESCASCinUseILimitGroupByNoWhereWhere FromStart sdSetClausesdLockingClausesdHavingClausesdDistinctClause sdLimitClausesdOrderByClausesdGroupByClause sdWhereClause sdFromClauseQunQSqlBinOpCompositeErrorDeconstructionErrorNullPlaceholdersErrorMismatchingLengthsErrorUnexpectedCaseErrorOperationNotSupportedUnsafeSqlCaseErrorNewIdentForErrorInsertionFinalErrorUnsupportedSqlInsertIntoType MakeFromErrorEmptySqlExprValueListCompositeKeyErrorMakeHavingErrorMakeWhereError MakeExcErrorMakeOnClauseErrorSqlCastAsError SqlCaseError FoldHelpError MakeSetErrorCombineInsertionErrorToInsertionErrorNotErrorSqlBinOpCompositeErrUnexpectedCaseErrCompositeKeyErrfromPreprocessfrom_finalR KnowResultparensM fieldNamesetAuxsub fromDBName existsHelperifNotEmptyList countHelperuncommas intersperseBmakeInsertInto makeSelectmakeFrommakeSet makeWhere makeGroupBy makeHaving makeOrderBy makeLimit makeLocking getEntityValfrom3Pfrom3to3from4Pfrom4to4from5Pto5from6Pto6from7Pto7from8Pto8from9Pto9from10Pto10from11Pto11from12Pto12from13Pto13from14Pto14from15Pto15from16Pto16fmappure emptyArray Data.StringIsString Data.Foldablenull$fPersistFieldSqlJSONB$fPersistFieldJSONB$fNumJSONAccessor fromIntegerfromPersistValueErrorfromPersistValueParseErrornumErrbadParseNothing text-1.2.3.1Data.Text.InternalTextversion getBinDir getLibDir getDynLibDir getDataDir getLibexecDir getSysconfDirgetDataFileName