Do you have to keep that there permanently or just when testing? On Tue, Mar 20, 2012 at 8:54 AM, Bruno Rocha <rochacbr...@gmail.com> wrote:
> have you tried fake_migrate=True ? > > > On Tue, Mar 20, 2012 at 12:50 PM, Bruce Wade <bruce.w...@gmail.com> wrote: > >> Hi, >> >> This one error is starting to become a pain, is there anyway we can >> provide a better solution. For example if the table already exists why just >> NOT create it instead of throwing an error? >> >> For example I have one database table created from when I was testing an >> application say "main". Then I created a specific application that will >> actually handle all the databases that main was using called "support". >> However now when I run support I get the error >> the psycopg2.ProgrammingError: relation "support_topics" already exists. >> Ideally the code would be smart enough to know we don't want to re-create >> that table. I am assuming this error is there to help prevent >> the accidental overwrite of a table. However it is causing me more problems >> then it is worth. >> >> What if we had an option were we can turn that error off and on? >> Currently I have 5 developers working on a project so sometimes when they >> commit code I need to delete my database and rebuild just to prevent this >> error. >> >> -- >> -- >> Regards, >> Bruce Wade >> http://ca.linkedin.com/in/brucelwade >> http://www.wadecybertech.com >> http://www.warplydesigned.com >> http://www.fitnessfriendsfinder.com >> > > > > -- > > Bruno Rocha > [http://rochacbruno.com.br] > > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.warplydesigned.com http://www.fitnessfriendsfinder.com
