Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS SQL server implementation produce DROP COLUMN queries without schema #284

Closed
sqlalchemy-bot opened this issue Mar 11, 2015 · 4 comments
Closed
Labels
bug Something isn't working op directives

Comments

@sqlalchemy-bot
Copy link

Migrated issue, originally created by dmazhar

Hi. I have such lines in my autogenerated migration script:

op.drop_column(u'asset_ID', 'asset_type', schema=u'HARDWARE')

It's in downgrade section, and when I'm running downgrade it produces next SQL query:

ALTER TABLE [asset_ID] DROP COLUMN asset_type;

So the schema was omitted in this query and migration fails.

@sqlalchemy-bot
Copy link
Author

Michael Bayer (@zzzeek) wrote:

6235698

@sqlalchemy-bot
Copy link
Author

Changes by Michael Bayer (@zzzeek):

  • changed status to closed

@sqlalchemy-bot
Copy link
Author

Michael Bayer (@zzzeek) wrote:

thank you

@sqlalchemy-bot
Copy link
Author

dmazhar wrote:

Thanks Mike. You're super fast.

@sqlalchemy-bot sqlalchemy-bot added op directives bug Something isn't working labels Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working op directives
Projects
None yet
Development

No branches or pull requests

1 participant