On 11/08/2015 05:42 AM, Ofir Herzas wrote: > Changing a VARCHAR column to CLOB (TEXT) raises the following exception > under Oracle: > > | > sqlalchemy.exc.DatabaseError:(cx_Oracle.DatabaseError)ORA-22858:invalid > alteration of datatype > [SQL:'ALTER TABLE tab MODIFY col CLOB'] > > | > > While this is an Oracle fault, it would be nice if the abstraction layer > took care of it. > > The proposed solution that I found was to add a new clob column, copy > the data, remove the old column and rename
Alembic offers a rough version of this feature in the form of "batch migrations", but that involves a whole table copy. Recipes like adding new columns and copying data can be achieved using custom directives, see http://alembic.readthedocs.org/en/latest/cookbook.html#replaceable-objects for an example of how to make new directives. I will gladly accept documentation illustrating a recipe for this behavior. > > -- > You received this message because you are subscribed to the Google > Groups "sqlalchemy-alembic" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to sqlalchemy-alembic+unsubscr...@googlegroups.com > <mailto:sqlalchemy-alembic+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
