diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-04-30 15:17:18 -0400 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-04-30 15:17:18 -0400 |
commit | 17b7299729fe1ff05e1638d555233875bc21caab (patch) | |
tree | f6ffbcbac40b280ec2ee691258ac156b7d67d891 /alembic/environment.py | |
parent | 22c36646b82ab1c4d076fc52e4c7e741ca56567c (diff) | |
download | alembic-17b7299729fe1ff05e1638d555233875bc21caab.tar.gz |
- [feature] Basic support for Oracle added,rel_0_3_2
courtesy shgoh. #40
Diffstat (limited to 'alembic/environment.py')
-rw-r--r-- | alembic/environment.py | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/alembic/environment.py b/alembic/environment.py index 52c353a..ab7a7d4 100644 --- a/alembic/environment.py +++ b/alembic/environment.py @@ -373,14 +373,16 @@ class EnvironmentContext(object): Parameters specific to individual backends: :param mssql_batch_separator: The "batch separator" which will - be placed - between each statement when generating offline SQL Server + be placed between each statement when generating offline SQL Server migrations. Defaults to ``GO``. Note this is in addition to the - customary - semicolon ``;`` at the end of each statement; SQL Server considers - the "batch separator" to denote the end of an individual statement - execution, and cannot group certain dependent operations in - one step. + customary semicolon ``;`` at the end of each statement; SQL Server + considers the "batch separator" to denote the end of an + individual statement execution, and cannot group certain + dependent operations in one step. + :param oracle_batch_separator: The "batch separator" which will + be placed between each statement when generating offline + Oracle migrations. Defaults to ``/``. Oracle doesn't add a + semicolon between statements like most other backends. """ opts = self.context_opts |