Re: Autogenerate ALWAYS assumes an empty schema with Oracle 11.2

2016-01-03 Thread Nana Okyere
My goodness! That was it! I created and used a standard user in Oracle and things worked as expected. Thanks a bunch. The more I run into some of these things, the more I dislike Oracle. Right on Michael, I learn, test, develop against Oracle XE because we use Oracle at work so I have to live

Autogenerate ALWAYS assumes an empty schema with Oracle 11.2

2016-01-02 Thread Nana Okyere
Disclosure: I'm a newbie :-) Starting with an empty table, I autogenerate and then do upgrade and it works fine the first time. When I make a small change to the model(s) like adding a new column, then I do autogenerate, alembic generates the upgrade and downgrade code as if starting from

Autogenerate ALWAYS assumes an empty schema with Oracle 11.2

2016-01-02 Thread Nana Okyere
Disclosure: I'm a newbie :-) Starting with an empty table, I autogenerate and then do upgrade and it works fine the first time. When I make a small change to the model(s) like adding a new column, then I do autogenerate, alembic generates the upgrade and downgrade code as if starting from

Re: Autogenerate ALWAYS assumes an empty schema with Oracle 11.2

2016-01-02 Thread Mike Bayer
On 01/02/2016 01:18 PM, Nana Okyere wrote: > Disclosure: I'm a newbie :-) > > Starting with an empty table, I autogenerate and then do upgrade and it > works fine the first time. When I make a small change to the model(s) > like adding a new column, then I do autogenerate, alembic generates

Re: Autogenerate ALWAYS assumes an empty schema with Oracle 11.2

2016-01-02 Thread Nana Okyere
The tables are not in an explicitly named schema. By default, it uses the schema of the user logged in. Looking at the debug output on the console, I can see that it uses the correct schema i.e. SYSTEM. I set the logging to debug and went through the whole process. I'll attach the entire