3 tg @sddlmZddlZddlmZddlmZddlmZej Z ee j ej dZ ddZ e jd ee jjd d ejd jZd dZddZddZejrenedS))with_statementN) fileConfig) current_app)contextz alembic.envc Cs4ytjdjjStk r.tjdjjSXdS)Nmigrate)r extensionsdb get_engine TypeErrorenginer r migrations/env.pyr sr zsqlalchemy.url%z%%rcCsttdrtjdStjS)N metadatas)hasattr target_dbrmetadatar r r r get_metadata+s  rc Cs<tjd}tj|tddtjtjWdQRXdS)aFRun migrations in 'offline' mode. This configures the context with just a URL and not an Engine, though an Engine is acceptable here as well. By skipping the Engine creation we don't even need a DBAPI to be available. Calls to context.execute() here emit the given string to the script output. zsqlalchemy.urlT)urltarget_metadata literal_bindsN)configget_main_optionr configurerbegin_transactionrun_migrations)rr r r run_migrations_offline1s  rcCsddd}t}|jD}tjf|t|dtjdjtjtj WdQRXWdQRXdS)zRun migrations in 'online' mode. In this scenario we need to create an Engine and associate a connection with the context. cSs:ttjddr6|d}|jjr6g|dd<tjddS)N autogenerateFrzNo changes in schema detected.)getattrrcmd_opts upgrade_opsis_emptyloggerinfo)rrevision directivesscriptr r r process_revision_directivesQs   z:run_migrations_online..process_revision_directives) connectionrr'rN) r connectrrrrrconfigure_argsrr)r' connectabler(r r r run_migrations_onlineFs   r,) __future__rloggingZlogging.configrflaskralembicrrconfig_file_name getLoggerr"r set_main_optionstrrreplacerrrrrr,is_offline_moder r r r s"