File: //opt/alt/python27/lib/python2.7/site-packages/alembic/templates/pylons/env.pyo
�
�M!Vc @ s� d Z d d l m Z d d l m Z d d l m Z d d l m Z y d d l m
Z e d Wn? e j
Z
e
j d � Z
e e
� e d e
d
d �Z n Xe d e j
d
� j j Z d Z d � Z d � Z e j � r� e � n e � d S( s| Pylons bootstrap environment.
Place 'pylons_config_file' into alembic.ini, and the application will
be loaded from there.
i����( t context( t loadapp( t
fileConfig( t Engine( t configt __file__t pylons_config_files config:%st relative_tot .s
%s.model.metas pylons.packagec C sC t j d t j j d t d t � t j � � t j � Wd QXd S( sF Run 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.
t urlt target_metadatat
literal_bindsN( R t configuret metat engineR R
t Truet begin_transactiont run_migrations( ( ( sM /opt/alt/python27/lib/python2.7/site-packages/alembic/templates/pylons/env.pyt run_migrations_offline$ s
c C sX t d � � t j � �: } t j d | d t � t j � � t j � Wd QXWd QXd S( s� Run migrations in 'online' mode.
In this scenario we need to create an Engine
and associate a connection with the context.
s'