Îõ³h&èÅ      !"#$%&'()*+,-./0123456789:;<=>?@ABCD/(c) 2014 Andreas Meingast  BSD-styleandre@andrevdm.com experimentalGHC Safe-Inferred"Œpostgresql-migration?Checks if the table with the given name exists in the database.postgresql-migrationñExecutes the given IO monad inside a transaction and performs a roll-back afterwards (even if exceptions occur)./(c) 2014 Andreas Meingast  BSD-styleandre@andrevdm.com experimentalGHC Safe-Inferred"89:ã#*postgresql-migration/A product type representing a single, executed .postgresql-migration#The name of the executed migration.postgresql-migration3The calculated MD5 checksum of the executed script.postgresql-migrationÄA timestamp without timezone of the date of execution of the script. postgresql-migrationVerbosity of the library. postgresql-migrationÍThe name of the table that stores the migrations, usually "schema_migrations" postgresql-migrationLogger. E indicates log level, F for an error message and G for an info message. postgresql-migration&If/when transactions should be started postgresql-migrationòDetermines how transactions are handled Its is recommened to use transaction when running migrations Certain actions require a transaction per script, if you are doing this use TransactionPerStep If you want a single transaction for all migrations use TransactionPerRun If you do not want a transaction, or are using an existing transaction then use NoNewTransactionpostgresql-migrationäNo new transaction will be started. Up to the caller to decide if the run is in a transaction or notpostgresql-migrationCall H once for the entire postgresql-migrationCall H once for each step in a " (i.e. new transaction per script)postgresql-migration.A sum-type denoting the result of a migration.postgresql-migration'There was an error in script migration.postgresql-migration,All scripts have been executed successfully.Ipostgresql-migration5A sum-type denoting the result of a single migration.Jpostgresql-migrationÌThe script has already been executed and the checksums match. This is good.Kpostgresql-migrationÔThe script has already been executed and there is a checksum mismatch. This is bad.Lpostgresql-migration4The script has not been executed, yet. This is good.postgresql-migration determines the action of the   script.postgresql-migrationÊInitializes the database with a helper table containing meta information.postgresql-migration9Executes migrations based on SQL scripts in the provided M in alphabetical order.postgresql-migration>Executes a migration based on script located at the provided M.postgresql-migration6Executes a migration based on the provided bytestring.postgresql-migration?Validates that the provided MigrationCommand has been executed.postgresql-migrationPerforms a series of s in sequence.postgresql-migrationÝThe name of a script. Typically the filename or a custom name when using Haskell migrations.postgresql-migration(The checksum type of a migration script. postgresql-migration(Executes migrations inside the provided MigrationContext.Returns  if the provided Ê executes without error. If an error occurs, execution is stopped and a  is returned.!postgresql-migration Execute a sequence of migrationsReturns  if all of the provided Ìs execute without error. If an error occurs, execution is stopped and the  is returned.Npostgresql-migration%Implements runMigration. Ensure that O is only called on the first runPpostgresql-migrationImplements runMigrations"postgresql-migration9Run a sequence of contexts, stopping on the first failureQpostgresql-migration?Executes all SQL-file based migrations located in the provided dir in alphabetical order.Rpostgresql-migrationLists all files in the given M dir in alphabetical order.Spostgresql-migration9Executes a generic SQL migration for the provided script name with content contents.Tpostgresql-migrationëInitializes the database schema with a helper table containing meta-information about executed migrations.Upostgresql-migration Validates a 3. Validation is defined as follows for these types:6: validate the presence of the meta-information table.Ñ: validate the presence and checksum of all scripts found in the given directory.9: validate the presence and checksum of the given script.7: validate the presence and checksum of the given file.: always succeeds.?: validates all the sub-commands stopping at the first failure.Vpostgresql-migration4Checks the status of the script with the given name nameõ. If the script has already been executed, the checksum of the script is compared against the one that was executed. If there is no matching script entry in the database, the script will be executed and its meta-information will be recorded.Wpostgresql-migrationËCalculates the MD5 checksum of the provided bytestring in base64 encoding.$postgresql-migration Produces a list of all executed (s in the default schema_migrations table%postgresql-migration Produces a list of all executed s.!postgresql-migrationThe postgres connection to usepostgresql-migrationThe options for this migrationpostgresql-migrationThe commands to runPpostgresql-migration Is this the first/top-level callpostgresql-migrationThe postgres connection to usepostgresql-migrationThe options for this migrationpostgresql-migrationThe commands to run$  !"#$%$# !"  $%/(c) 2014 Andreas Meingast  BSD-styleandre@andrevdm.com experimentalGHC Safe-Inferred"ž>postgresql-migrationThe >. provides an execution context for migrations.@postgresql-migration%The action that will be performed by CApostgresql-migrationVerbosity of the library.Bpostgresql-migration0The PostgreSQL connection to use for migrations.Dpostgresql-migrationRun in verbose modepostgresql-migrationThe postgres connection to usepostgresql-migrationThe commands to run"$>?@ABCDCD">?@AB$ Safe-InferredùXYZ[\]^_à       !"#$%&'()*+,-./0123456789:;<=>?@AABCD#$EFGEFHEFIJKLMNOPEQRSTUVWXYZ[\]^_`abcdå$postgresql-migration-0.2.1.6-inplaceDatabase.PostgreSQL.Simple.Util$Database.PostgreSQL.Simple.Migration-Database.PostgreSQL.Simple.Migration.V1CompatPaths_postgresql_migration existsTablewithTransactionRolledBackSchemaMigrationschemaMigrationNameschemaMigrationChecksumschemaMigrationExecutedAtMigrationOptions optVerbose optTableName optLogWriteroptTransactionControlTransactionControlNoNewTransactionTransactionPerRunTransactionPerStep VerbosityVerboseQuietMigrationResultMigrationErrorMigrationSuccessMigrationCommandMigrationInitializationMigrationDirectory MigrationFileMigrationScriptMigrationValidationMigrationCommands ScriptNameChecksum runMigration runMigrationssequenceMigrationsdefaultOptions getMigrationsgetMigrations'$fMonoidMigrationCommand$fSemigroupMigrationCommand$fToRowSchemaMigration$fFromRowSchemaMigration$fOrdSchemaMigration$fShowSchemaMigration$fEqSchemaMigration$fReadSchemaMigration$fShowTransactionControl$fShowVerbosity $fEqVerbosity$fShowMigrationResult$fEqMigrationResult$fReadMigrationResult$fOrdMigrationResult$fFunctorMigrationResult$fFoldableMigrationResult$fTraversableMigrationResult$fShowCheckScriptResult$fShowExpectedVsActual$fShowMigrationCommand$fEqMigrationCommand$fReadMigrationCommand$fOrdMigrationCommandMigrationContextmigrationContextCommandmigrationContextVerbosemigrationContextConnectionbase Data.EitherEitherLeftRightØpostgresql-simple-0.6.4-450ab67f5eb961526d54d2a51a913dbcae87c2457f100b4a9a9b4503a6b78085&Database.PostgreSQL.Simple.TransactionwithTransactionCheckScriptResultScriptOkScriptModifiedScriptNotExecutedGHC.IOFilePath runMigration'doRunTransactionrunMigrations'executeDirectoryMigrationscriptsInDirectoryexecuteMigrationinitializeSchemaexecuteValidation checkScriptmd5HashversiongetDataFileName getBinDir getLibDir getDynLibDir getDataDir getLibexecDir getSysconfDir