h,      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ 0.5.4.0None")*078:=U.Specifies how we should handle lock conflicts.See  https://www.postgresql.org/docs/9.5/static/sql-select.html#SQL-FOR-UPDATE-SHAREthe manual section for more informationVNOWAIT2. Report an error rather than waiting for the lockW SKIP LOCKED3. Rather than wait for a lock, skip the row insteadXSpecifies the level of lock that will be taken against a row. See  https://www.postgresql.org/docs/current/static/explicit-locking.html#LOCKING-ROWSthe manual section for more information.Y UPDATEZ  NO KEY UPDATE[ SHARE\  KEY SHARE for Postgres for Postgres for Postgres for PostgresRepresentation of an arbitrary Postgres command. This is the combination of the command syntax (repesented by 3), as well as the type of command (represented by ). The command type is necessary for us to know how to retrieve results from the database.A piece of Postgres SQL syntax, which may contain embedded escaped byte and text sequences. / composes monoidally, and may be created with , , ,  escapBytea, and .Postgres TypeInfo for tsvector TODO Is the Oid stable from postgres instance to postgres instance?LIMIT OFFSET )*+,-./01ABDC=>@?JKLfghOPQRTSEFHIGrst{|}lmnijkopq6798bcde~2354]^_a`UVWX\Z[Y:;<MNuvwxyz !"#$%&'(~{|}bcedxyzuvwrstopqlmnijkfghOPQMNJKLEFIHGABDC=>@?:;<67982354/01,-.)*+&'(#$% !"]^a`_XYZ[\UVWRST None")*078=0The Postgres backend type, used to parameterize . See the definitions there for more information. The corresponding query monad is Pg. See documentation for  and the  !https://haskell-beam.github/beam/ user guide- for more information on using this backend.Deserialize integral fields, possibly downcasting from a larger numeric type via  if we won't lose data, and then falling back to any integral type via Deserialize integral fields, possibly downcasting from a larger integral type, but only if we won't lose data None")*/0178=Q2The type of Postgres regular expressions. Only a  instance is supplied, because you won't need to be reading these back from the database.3If you're generating regexes dynamically, then use 2 to convert a string expression into a regex one. Postgres MONEY" data type. A simple wrapper over , because Postgres money format is locale-dependent, and we don't handle currency symbol placement, digit grouping, or decimal separation.The - function can be used to convert a number to .Postgres provides separate json_ and jsonb_ functions. However, we know what we're dealing with based on the type of data, so we can be less obtuse.For more information on how these functions behave, see the Postgres manual section on  https://www.postgresql.org/docs/current/static/functions-json.htmlJSON.The  json_each or  jsonb_each function. Values returned as json or jsonb respectively. Use  to join against the resultLike #, but returning text values insteadThe json_object_keys and jsonb_object_keys function. Use  to join against the result.The json_array_elements and jsonb_array_elements function. Use  to join against the resultLike , but returning the values as   The  json_typeof or  jsonb_typeof functionThe json_strip_nulls or jsonb_strip_nulls function.The json_agg or  jsonb_agg aggregate.The json_object_agg or jsonb_object_agg. The first argument gives the key source and the second the corresponding values.Output row of  and Output row of "Key-value pair, used as output of  and  The Postgres JSONB type, which stores JSON-encoded data in a postgres-specific binary format. Like , the type parameter indicates the Haskell type which the JSON encodes.;Fields with this type are automatically given the Postgres JSONB type The Postgres JSON type, which stores textual values that represent JSON objects. The type parameter indicates the Haskell type which the JSON encodes. This type must be a member of  and  in order for deserialization and serialization to work as expected.The defaultMigratableDbSettings. function automatically assigns the postgres JSON type to fields with this type.A class representing Postgres Range types and how to refer to them when speaking to the database.For custom Range types, create an uninhabited type, and make it an instance of this class.$The range type name in the database.0A range of a given Haskell type (represented by a9) stored as a given Postgres Range Type (represented by n).A reasonable example might be Range PgInt8Range Int64&. This represents a range of Haskell Int64 values stored as a range of  in Postgres.Represents a single bound on a Range. A bound always has a type, but may not have a value (the absense of a value represents unbounded).Represents the types of bounds a range can have. A range can and often does have mis-matched bound types.If you are extending beam-postgres and provide another expression context that can be represented in an array, provide an empty instance of this class.An expression context that determines which types of expressions can be put inside an array element. Any scalar, aggregate, or window expression can be placed within an array.:A query that can be run against a document contained in a .-When this field is embedded in a beam table, defaultMigratableDbSettings$ will give the column the postgres TSVECTOR type7The identifier of a Postgres text search configuration.Use the . instance to construct new values of this typeThe type of a document preprocessed for full-text search. The contained ' is the Postgres representation of the TSVECTOR type. Use , to construct these on-the-fly from strings.-When this field is embedded in a beam table, defaultMigratableDbSettings$ will give the column the postgres TSVECTOR type. Postgres NOW()) function. Returns the server's timestamp Postgres ILIKE) operator. A case-insensitive version of . Postgres ILIKE) operator. A case-insensitive version of .A full-text search configuration with sensible defaults for english The Postgres  to_tsvector9 function. Given a configuration and string, return the TSVECTOR, that represents the contents of the string.Determine if the given TSQUERY* matches the document represented by the TSVECTOR. Behaves exactly like the similarly-named operator in postgres. The Postgres  to_tsquery9 function. Given a configuration and string, return the TSQUERY, that represents the contents of the string.3Index into the given array. This translates to the  array[ index] syntax in postgres. The beam operator name has been chosen to match the 'Data.Vector.(!)' operator. Postgres  array_dims() function. Returns a textual representation of the dimensions of the array.Return the upper or lower bound of the given array at the given dimension (statically supplied as a type application on a ). Note that beam will attempt to statically determine if the dimension is in range. GHC errors will be thrown if this cannot be proved.For example, to get the upper bound of the 2nd-dimension of an array: &arrayUpper_ @2 vectorValuedExpression Return the upper or lower bound of the given array at the given dimension (statically supplied as a type application on a ). Note that beam will attempt to statically determine if the dimension is in range. GHC errors will be thrown if this cannot be proved.For example, to get the upper bound of the 2nd-dimension of an array: &arrayUpper_ @2 vectorValuedExpression These functions can be used to find the lower and upper bounds of an array where the dimension number is not known until run-time. They are marked unsafe because they may cause query processing to fail at runtime, even if they typecheck successfully.These functions can be used to find the lower and upper bounds of an array where the dimension number is not known until run-time. They are marked unsafe because they may cause query processing to fail at runtime, even if they typecheck successfully.Get the size of the array at the given (statically known) dimension, provided as a type-level  . Like the  and  functions,throws a compile-time error if the dimension is out of bounds.Get the size of an array at a dimension not known until run-time. Marked unsafe as this may cause runtime errors even if it type checks. The Postgres @> operator. Returns true if every member of the second array is present in the first. The Postgres <@ operator. Returns true if every member of the first array is present in the second. Postgres ||= operator. Concatenates two vectors and returns their result.7Build a 1-dimensional postgres array from an arbitrary  containing expressions.4Build a 1-dimensional postgres array from a subqueryThe postgres range operator - . Postgres @> and <@ operators for JSON. Return true if the json object pointed to by the arrow is completely contained in the other. See the Postgres documentation for more in formation on what this means. Postgres @> and <@ operators for JSON. Return true if the json object pointed to by the arrow is completely contained in the other. See the Postgres documentation for more in formation on what this means.:Access a JSON array by index. Corresponds to the Postgres -> operator. See 2 for the corresponding operator for object access.8Acces a JSON object by key. Corresponds to the Postgres -> operator. See + for the corresponding operator for arrays.Access a JSON array by index, returning the embedded object as a string. Corresponds to the Postgres ->> operator. See , for the corresponding operator on objects.Access a JSON object by key, returning the embedded object as a string. Corresponds to the Postgres ->> operator. See + for the corresponding operator on arrays.Access a deeply nested JSON object. The first argument is the JSON object to look within, the second is the path of keys from the first argument to the target. Returns the result as a new json value. Note that the postgres function allows etiher string keys or integer indices, but this function only allows string keys. PRs to improve this functionality are welcome.Like $ but returns the result as a string. Postgres ? operator. Checks if the given string exists as top-level key of the json object. Postgres ?| and ?& operators. Check if any or all of the given strings exist as top-level keys of the json object respectively. Postgres ?| and ?& operators. Check if any or all of the given strings exist as top-level keys of the json object respectively. Postgres - operator on json objects. Returns the supplied json object with the supplied key deleted. See + for the corresponding operator on arrays. Postgres - operator on json arrays. See , for the corresponding operator on objects. Postgres #- operator. Removes all the keys specificied from the JSON object and returns the result. Postgres json_array_length function. The supplied json object should be an array, but this isn't checked at compile-time. Postgres  array_to_json function. The postgres  jsonb_set function.  pgJsonUpdate expects the value specified by the path in the second argument to exist. If it does not, the first argument is not modified.  will create any intermediate objects necessary. This corresponds to the create_missing argument of  jsonb_set) being set to false or true respectively. The postgres  jsonb_set function.  pgJsonUpdate expects the value specified by the path in the second argument to exist. If it does not, the first argument is not modified.  will create any intermediate objects necessary. This corresponds to the create_missing argument of  jsonb_set) being set to false or true respectively. Postgres  jsonb_pretty function>An aggregate that adds each value to the resulting array. See  pgArrayOver if you want to specify a quantifier. Corresponds to the Postgres  ARRAY_AGG function. Postgres  ARRAY_AGG with an explicit quantifier. Includes each row that meets the quantification criteria in the result. Postgres bool_or5 aggregate. Returns true if any of the rows are true. Postgres bool_and3 aggregate. Returns false unless every row is true.Joins the string value in each row of the first argument, using the second argument as a delimiter. See 1 if you want to provide explicit quantification. The Postgres  string_agg function, with an explicit quantifier. Joins the values of the second argument using the delimiter given by the third.Modify a query to only return rows where the supplied key function returns a unique value. This corresponds to the Postgres  DISTINCT ON support.,Attempt to pack a floating point value as a  value, paying no attention to the locale-dependent currency symbol, digit grouping, or decimal point. This will use the .! symbol as the decimal separator. Multiply a MONEY8 value by a numeric value. Corresponds to the Postgres * operator. Divide a MONEY3 value by a numeric value. Corresponds to Postgres / where the numerator has type MONEY and the denominator is a number. If you would like to divide two MONEY. values and have their units cancel out, use . Dividing two MONEY4 value results in a number. Corresponds to Postgres / on two MONEY% values. If you would like to divide MONEY by a scalar, use  Postgres + and - operators on money. Postgres + and - operators on money. The Postgres MONEY type can be summed or averaged in an aggregation. These functions provide the quantified aggregations. See  and  for the unquantified versions. The Postgres MONEY type can be summed or averaged in an aggregation. These functions provide the quantified aggregations. See  and  for the unquantified versions. The Postgres MONEY type can be summed or averaged in an aggregation. To provide an explicit quantification, see  and . The Postgres MONEY type can be summed or averaged in an aggregation. To provide an explicit quantification, see  and .Convert a string valued expression (which could be generated dynamically) into a  -typed one.(Match regular expression, case-sensitive*Match regular expression, case-insensitive1Does not match regular expression, case-sensitive3Does not match regular expression, case-insensitive Postgres regexp_replace. Replaces all instances of the regex in the first argument with the third argument. The fourth argument is the postgres regex options to provide. Postgres  regexp_match. Matches the regular expression against the string given and returns an array where each element corresponds to a match in the string, or NULL if nothing was found Postgres regexp_split_to_array. Splits the given string by the given regex and returns the result as an array. Postgres regexp_split_to_table. Splits the given string by the given regex and return a result set that can be joined against.>Join the results of the given set-valued function to the query,Introduce each element of the array as a rowIntroduce each element of the array as a row, along with the element's indexLower bound typeUpper bound type. Lower bound value. Upper bound valueNone")*78=hOThe most general kind of DELETE that postgres can performYou can build this from a  by using  'delete tbl where `returning` projectionRun the result with The most general kind of UPDATE that postgres can performYou can build this from a  by using  'update tbl where `returning` projectionRun the result with What to do when an INSERT( statement inserts a row into the table tbl that violates a constraint.The most general kind of INSERT that postgres can performCombines the result of a query along with a set of locked tables. Used as a return value for the  function.An explicit lock against some tables. You can create a value of this type using the  function. You can combine these values monoidally to combine multiple locks for use with the  function. Use with * to lock all tables mentioned in the queryReturn and lock the given tables. Typically used as an infix operator. See the  https://haskell-beam.github.io/beam/user-guide/backends/beam-postgres/the user guide for usage examples:Join with a table while locking it explicitly. Provides a  value that can be used with % to explicitly lock a table during a SELECT statementLock some tables during the execution of a query. This is rather complicated, and there are several usage examples in https://haskell-beam.github.io/beam/user-guide/backends/beam-postgres/the user guideThe Postgres locking clause is rather complex, and beam currently does not check several pre-conditions. It is assumed you kinda know what you're doing.4Things which postgres doesn't like, but beam will do9Using aggregates within a query that has a locking clauseUsing UNION,  INTERSECT, or EXCEPTSee  https://www.postgresql.org/docs/10/static/sql-select.html#SQL-FOR-UPDATE-SHAREhere for more details.*This function accepts a locking strength (UPDATE, SHARE,  KEY SHARE%, etc), an optional locking option (NOWAIT or  SKIP LOCKED), and a query whose rows to lock. The query should return its result wrapped in  , via the  or  function.If you want to use the most common behavior (lock all rows in every table mentioned), the # function may be what you're after.Like , but does not require an explicit set of locked tables. This produces an empty  FOR .. OF clause. The Postgres DEFAULT VALUES clause for the INSERT command.A  beam-postgres-specific version of >, which provides fuller support for the much richer Postgres INSERT% syntax. This allows you to specify  ON CONFLICT/ actions. For even more complete support, see .The full Postgres INSERT. syntax, supporting conflict actions and the RETURNING CLAUSE. See 2 for how to specify a conflict action or provide ' to preserve the behavior without any  ON CONFLICT clause. The last argument takes a newly inserted row and returns the expression to be returned as part of the  RETURNING clause. For a backend-agnostic version of this functionality see . Use runInsertReturning to get the results. Postgres  LATERAL JOIN support=Allows the use of variables introduced on the left side of a JOIN$ to be used on the right hand side.Because of the default scoping rules, we can't use the typical monadic bind (>>= ) operator to create this join. Instead,  takes two arguments. The first is the left hand side of the JOIN. The second is a function that takes the result of the first join and uses those variables to create the right hand side.For example, to join table A with a subquery that returns the first three rows in B which matches a column in A, ordered by another column in B: lateral_ (_tableA database) $ \tblA -> limit_ 3 $ ordering_ (\(_, b) -> asc_ (_bField2 b)) $ do b <- _tableB database guard_ (_bField1 b ==. _aField1 a) pure (a, b0By default, Postgres will throw an error when a conflict is detected. This preserves that functionality. Tells postgres what to do on an INSERT conflict. The first argument is the type of conflict to provide an action for. For example, to only provide an action for certain fields, use . Or to only provide an action over certain fields where a particular condition is met, use >. If you have a particular constraint violation in mind, use -. To perform an action on any conflict, use . See the  >https://www.postgresql.org/docs/current/static/sql-insert.htmlPostgres documentation.Perform the action only if the given named constraint is violated Postgres UPDATE ... RETURNING statement support. The last argument takes the newly inserted row and returns the values to be returned. Use runUpdateReturning to get the results. Postgres DELETE ... RETURNING statement support. The last argument takes the newly inserted row and returns the values to be returned. Use runDeleteReturning to get the results.4UVWX\Z[Y4XYZ[\UVWNone")*78=t4 Postgres-specific database predicate asserting the existence of an extension in the database. The  properly provides CREATE EXTENSION and DROP EXTENSION$ statements to the migration finder.2Type class implemented by any Postgresql extensionReturn the name of this extension. This should be the string that is passed to CREATE EXTENSION. For example, PgCrypto returns  "pgcrypto".Return a value of this extension type. This should fill in all fields in the record. For example, PgCrypto builds a record where each function wraps the underlying Postgres one.&Represents an extension in a database.For example, to include the Database.Beam.Postgres.PgCrypto extension in a database, import Database.Beam.Postgres.PgCrypto data MyDatabase entity = MyDatabase { _table1 :: entity (TableEntity Table1) , _cryptoExtension :: entity (PgExtensionEntity PgCrypto) } migratableDbSettings :: CheckedDatabaseSettings Postgres MyDatabase migratableDbSettings = defaultMigratableDbSettings dbSettings :: DatabaseSettings Postgres MyDatabase dbSettings = unCheckDatabase migratableDbSettings -Note that our database now only works in the  backend.Extensions are implemented as records of functions and values that expose extension functionality. For example, the pgcrypto extension (implemented by PgCrypto*) provides cryptographic functions. Thus, PgCrypto is a record of functions over 3 which wrap the underlying postgres functionality.You get access to these functions by retrieving them from the entity in the database.For example, to use the pgcrypto! extension in the database above: let PgCrypto { pgCryptoDigestText = digestText , pgCryptoCrypt = crypt } = getPgExtension (_cryptoExtension dbSettings) in fmap_ (tbl -> (tbl, crypt (_field1 tbl) (_salt tbl))) (all_ (table1 dbSettings)) To implement your own extension, create a record type, and implement the  type class.Get the extension record from a database entity. See the documentation for . representing the Postgres CREATE EXTENSION command. Because the extension name is statically known by the extension type and  type class, this simply produces the checked extension entity.If you need to use the extension in subsequent migration steps, use  and " to get access to the underlying . representing the Postgres DROP EXTENSION. After this executes, you should expect any further uses of the extension to fail. Unfortunately, without linear types, we cannot check this.4There are no fields to rename when defining entitiesNone")*78=?tNone")*/78:=w in which we can run Postgres commands. See the documentation for  on examples of how to use. beam-postgres; also provides functions that let you run queries without . These functions may be more efficient and offer a conduit API. See Database.Beam.Postgres.Conduit for more information.You can execute  actions using  or .How to fetch results.4Fetch in batches of ~256 rows via cursor for SELECT.Fetch all rows at once. for the standard  postgresql: URI scheme. See the postgres documentation for more details on the formatting. See documentation for 2 for more information on how to use this with beamNone")*178=?w'Top-level migration backend for use by  beam-migrate toolsBeamDeserializers for postgres-specific types: Converts postgres DatabasePredicates to DatabasePredicates in the Haskell syntax. Allows automatic generation of Haskell schemas from postgres constraints.Turn a E into the corresponding . This is a best effort guess, and may fail on more exotic types. Feel free to send PRs to make this function more robust!Turn a series of  into a line-by-line array of #s suitable for writing to a script.!Write the migration given by the  to a file. for tsquery. See  for more information for tsvector. See  for more information for Postgres TEXT. characterLargeObject" is also mapped to this data type for Postgres BYTEA. binaryLargeObject" is also mapped to this data type) for a Postgres array without any bounds.Note that array support in  beam-migrate is still incomplete. for JSON. See  for more information for JSONB. See  for more information for UUID columns. The pgCryptoGenRandomUUID function in the PgCrypto3 extension can be used to generate UUIDs at random. for MONEY columns. Postgres SERIAL5 data types. Automatically generates an appropriate DEFAULT clause and sequence Postgres SERIAL5 data types. Automatically generates an appropriate DEFAULT clause and sequence Postgres SERIAL5 data types. Automatically generates an appropriate DEFAULT clause and sequenceNone")*078=Type class for Sql* types that can be turned into Postgres syntax, for use in the following debugging functions These includeNone"')*78=cRun a PostgreSQL SELECT statement in any .Run a PostgreSQL SELECT statement in any .Run a PostgreSQL INSERT statement in any '. Returns the number of rows affected.Run a PostgreSQL INSERT ... RETURNING ... statement in any  and get a  of the newly inserted rows.Run a PostgreSQL INSERT ... RETURNING ... statement in any  and get a  of the newly inserted rows.Run a PostgreSQL UPDATE statement in any '. Returns the number of rows affected.Run a PostgreSQL UPDATE ... RETURNING ... statement in any  and get a  of the newly updated rows.Run a PostgreSQL UPDATE ... RETURNING ... statement in any  and get a  of the newly updated rows.Run a PostgreSQL DELETE statement in any '. Returns the number of rows affected.Run a PostgreSQl DELETE ... RETURNING ... statement in any  and get a  of the deleted rows.Run a PostgreSQl DELETE ... RETURNING ... statement in any  and get a  of the deleted rows.9Run any DML statement. Return the number of rows affected+Runs any query that returns a set of values+Runs any query that returns a set of valuesNone")*78=  None")*78=None")*78=4Data type representing definitions contained in the pgcrypto extension*Each field maps closely to the underlying pgcrypto: function, which are described in further detail in the  --@>-<@-<@--&&--<<-->>--&<--&>---|---+--*--.-rLower_rUpper_isEmpty_ lowerInc_ upperInc_ lowerInf_ upperInf_ rangeMerge_range_@><@->#->$->>#->>$#>#>>??|?& withoutKey withoutIdx withoutKeyspgJsonArrayLength pgArrayToJson pgJsonbUpdate pgJsonbSet pgJsonbPretty pgArrayAggpgArrayAggOverpgBoolOr pgBoolAnd pgStringAggpgStringAggOverpgNubBy_pgMoney pgScaleMoney_pgDivideMoney_pgDivideMoneys_ pgAddMoney_pgSubtractMoney_pgSumMoneyOver_pgAvgMoneyOver_ pgSumMoney_ pgAvgMoney_pgRegex_~.~*.!~.!~*.pgRegexpReplace_pgRegexpMatch_pgRegexpSplitToArraypgRegexpSplitToTablepgUnnest pgUnnestArraypgUnnestArrayWithOrdinalitycentury_decade_dow_doy_epoch_isodow_isoyear_ microseconds_ milliseconds_ millennium_quarter_week_(Database.Beam.Backend.SQL.BeamExtensionsonConflictUpdateAllonConflictUpdateInsteadBeamHasInsertOnConflictSqlConflictActionSqlConflictTarget anyConflictconflictingFieldsconflictingFieldsWhereinsertOnConflictonConflictDoNothingonConflictUpdateSetonConflictUpdateSetWhere PgReturningPgReturningType returningPgDeleteReturningPgUpdateReturningPgUpdateReturningEmptyPgInsertOnConflictPgInsertReturningPgInsertReturningEmpty PgWithLockingPgLockedTableslockAll_ withLocks_locked_ lockingFor_lockingAllTablesFor_insertDefaultsinsertReturningrunPgInsertReturningListlateral_onConflictDefault onConflictconflictingConstraintupdateReturningrunPgUpdateReturningListdeleteReturningrunPgDeleteReturningList!$fBeamHasInsertOnConflictPostgres-$fProjectibleWithPredicatecberesPgWithLocking$fPgReturningSqlDelete$fPgReturningSqlUpdate$fPgReturningSqlInsert$fSemigroupPgLockedTables$fMonoidPgLockedTables IsPgExtensionpgExtensionNamepgExtensionBuildPgExtensionEntitygetPgExtensionpgCreateExtensionpgDropExtensionIsPgCustomDataTypepgDataTypeNamepgDataTypeDescriptionPgDataTypeSchema PgTypeCheckPgTypepgCustomEnumSchemapgBoundedEnumSchemapgCustomEnumActionProviderpgCreateEnumActionProviderpgDropEnumActionProviderpgChecksForTypeSchema createEnumpgEnumValueSyntax pgParseEnumbeamTypeForCustomPg$fRenamableWithRuleFieldRenamer'$fIsCheckedDatabaseEntityPostgresPgType $fIsDatabaseEntityPostgresPgType$fFromFieldPgRawString#$fFromBackendRowPostgresPgRawStringPgpostgresUriSyntaxliftIOWithHandlerunBeamPostgresDebugrunBeamPostgresmigrationBackendpostgresDataTypeDeserializerspgPredConverter pgTypeToHs migrateScriptwriteMigrationScriptpgDataTypeFromAttgetDbConstraintsgetDbConstraintsForSchemastsquerytsvectortextbyteaunboundedArrayjsonjsonbuuidmoneypointline lineSegmentbox smallserialserial bigserial!$fBeamSqlBackendHasSerialPostgres+$fFieldReturnTypeFalseFalsePostgresresTyFUN$fGenericSchemaName$fFromRowSchemaName PgDebugStmt pgTraceStmtIOpgTraceStmtIO' pgTraceStmtstreamingRunSelect runSelect runInsertstreamingRunInsertReturningrunInsertReturning runUpdatestreamingRunUpdateReturningrunUpdateReturning runDeletestreamingRunDeleteReturningrunDeleteReturningexecuteStatementstreamingRunQueryReturningrunQueryReturningPgCryptopgCryptoGenRandomUUIDpgCryptoGenRandomBytespgCryptoDearmor pgCryptoArmorpgCryptoPgpKeyIdpgCryptoPgpPubDecryptByteapgCryptoPgpPubDecryptpgCryptoPgpPubEncryptByteapgCryptoPgpPubEncryptpgCryptoPgpSymDecryptByteapgCryptoPgpSymDecryptpgCryptoPgpSymEncryptByteapgCryptoPgpSymEncryptpgCryptoGenSalt pgCryptoCryptpgCryptoHmacBytespgCryptoHmacTextpgCryptoDigestBytespgCryptoDigestText$fIsPgExtensionPgCryptoUuidOssppgUuidGenerateV5pgUuidGenerateV4pgUuidGenerateV3pgUuidGenerateV1McpgUuidGenerateV1 pgUuidNsX500 pgUuidNsOid pgUuidNsUrl pgUuidNsDns pgUuidNil$fIsPgExtensionUuidOsspIsSql92UpdateSyntaxIsSql92DeleteSyntaxIsSql92InsertSyntaxIsSql92SelectSyntaxDatabase.Beam.Backend.SQL MonadBeamscientific-0.3.8.0-823273e8269b4d3e3d6a3ac02931d04e5cb124de6146ead5b1e6e65252c72410Data.Scientific Scientific ghc-bignumGHC.Num.IntegerIntegerbytestring-0.12.1.0-f8cdData.ByteString.Internal.Typeaeson-2.2.3.0-857f234b561b6a026bf24b891adfc00427dbe16433930a14258ec9051fb1e7adData.Aeson.Types.FromJSONFromJSONData.Aeson.Types.ToJSONToJSONDatabase.Beam.Query.DataTypesbigint ghc-internalGHC.Internal.Data.StringIsStringDatabase.Beam.Query.Operatorlike_like_'GHC.Internal.TypeNatsGHC.Internal.Data.FoldableFoldable SqlDelete SqlUpdateMonadBeamInsertReturningPgHasExtensionpgExtensionActionProviderDatabase.Beam.Query.InternalQGenExprbeam-migrate-0.5.3.0-inplaceDatabase.Beam.Migrate.Types Migration+Database.Beam.Migrate.Types.CheckedEntitiesunCheckDatabase.Beam.Schema.TablesDatabaseEntitypgCreateExtensionProviderpgDropExtensionProviderDatabaseEntityDescriptorPgDatabaseExtensionCheckedDatabaseEntityDescriptorCheckedPgExtension FetchModeCursorBatchingAtOnceDatabase.Beam.Backend.URIBeamURIOpeners getFieldspgRenderSyntaxrunPgRowReader withPgDebugrunPgPgF PgFetchNextPgLiftIOPgLiftWithHandlePgRunReturningDatabase.Beam.Haskell.Syntax HsDataType SqlSelect SqlInsert pgStmtSyntaxbaseControl.Monad.IO.ClassMonadIOfuncELiftPgPgExpr