Actually, looking at the web2py manual, I shouldn't have to specify migrate=False. If the table exists and corresponds to the definition, it should do nothing. Anyone know why this is not the case when using postgresql?
-jason On Feb 17, 4:09 pm, jlegler <jleg...@gmail.com> wrote: > Oops, should have searched the forum before posting. It looks like I > just need to put migrate-False in my table definitions. However, that > does prompt a follow up question. > > If I use migrate=False in each of my tables and then modify my tables > at a future date, will it update the tables or just ignore them? > > -jason > > On Feb 17, 4:03 pm, jlegler <jleg...@gmail.com> wrote: > > > I've been developing a webapp against sqlite and in the process of > > moving it to postgresql for production I have run into some problems. > > This is the latest one: > > > When using postgresql, web2py is complaining that tables defined in my > > model already exist. > > For example, when I call: > > > auth.define_tables() > > > I get an error saying: > > > ProgrammingError: relation "auth_user" already exists. > > > If I put an if statement on that function call, it simply moves down > > the file to the next table definition and throws a similar error. Why > > is this happening in postgresql and not sqlite? I am seriously > > considering trying out mysql. Is anyone out there using postgresql > > successfully? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
