[openstack-dev] [Ceilometer] Need help with Alembic...
jaypipes at gmail.com
Mon Aug 26 19:15:37 UTC 2013
I just noticed that every single test case for SQL-driver storage is
executing every single migration upgrade before every single test case run:
instead of simply creating a new database schema from the models in the
current source code base using a call to sqlalchemy.MetaData.create_all().
This results in re-running migrations over and over again, instead of
having dedicated migration tests that would test each migration
individually, as is the case in projects like Glance...
Is this intentional?
On 08/26/2013 02:59 PM, Sandy Walsh wrote:
> I'm getting the same problem with a different migration (mine is
> complaining that a column already exists)
> I've compared it to the other migrations and it seems fine.
> On 08/26/2013 02:34 PM, Jay Pipes wrote:
>> Hey all,
>> I'm trying to figure out what is going wrong with my code for this patch:
>> I had previously added a sqlalchemy-migrate migration script to add an
>> event_type table, and had that working, but then was asked to instead
>> use Alembic for migrations. So, I removed the sqlalchemy-migrate
>> migration file and added an Alembic migration .
>> Unfortunately, I am getting the following error when running tests:
>> OperationalError: (OperationalError) table event_type already exists
>> u'\nCREATE TABLE event_type (\n\tid INTEGER NOT NULL, \n\t"desc"
>> VARCHAR(255), \n\tPRIMARY KEY (id), \n\tUNIQUE ("desc")\n)\n\n' ()
>> The migration adds the event_type table. I've seen this error occur
>> before when using SQLite due to SQLite's ALTER TABLE statement not
>> allowing the rename of a column. In the sqlalchemy-migrate migration, I
>> had a specialized SQLite migration upgrade  and downgrade  script,
>> but I'm not sure how I am supposed to handle this in Alembic. Could
>> someone help me out?
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev