oracle wrongly assumes transactiona ddl #245
Comments
Michael Bayer (@zzzeek) wrote: cant reproduce (edit: do you mean, you want tranasctional DDL, or you dont? right now we have it as transactional DDL is supported, so there is not a COMMIT after each statement. though I'm not recalling if Oracle supports it or not). given:
url is sqlalchemy.url = oracle://scott:tiger@xe output of a full upgrade:
there's no COMMIT after each statement. only one at the end. |
Michael Bayer (@zzzeek) wrote: plus you can set it to whichever one you want: http://alembic.readthedocs.org/en/rel_0_6/api.html#alembic.environment.EnvironmentContext.configure.params.transactional_ddl |
Michael Bayer (@zzzeek) wrote: when you say "before" and "after", I think you are actually just observing what Oracle does. That's not us. see https://asktom.oracle.com/pls/asktom/f?p=100:11:0%3A%3A%3A%3AP11_QUESTION_ID:7072180788422. |
Michael Bayer (@zzzeek) wrote: and then we finally see how you've really taken up a lot of my time by being so terse. you're saying you want our flag to match theirs. thanks for the clarity. |
Changes by Michael Bayer (@zzzeek):
|
Migrated issue, originally created by Ronny Pfannschmidt (@RonnyPfannschmidt)
oracle will commit before/after each ddl statement
The text was updated successfully, but these errors were encountered: