I am still on web2py 1.99.4. Perhaps that is the reason. For now my solution was to manually update the postgres database and use fake_migrate to create the corresponding .table files. http://web2py.com/books/default/chapter/29/06#Fixing-broken-migrations
I also develop with sqlite and migrations work there fine. On Thu, Nov 15, 2012 at 4:00 PM, LightDot <[email protected]> wrote: > I use postgre on almost all web2py projects and migrations work as expected. > I'm not really sure what combination of options are you looking for... I > generally recommend a simple approach - during the development, keep > migration settings at default. Once the database schema is finalized, turn > the migrations off to speed web2py up. That's it, nothing else to do... > Unless one has specific needs, this simple approach should work for almost > any project. > > When there's a need to change the db schema afterwards, simply turn the > migrations back on temporarily and then turn them back off when done. I had > situations when I needed to use fake migrations in order to incorporate some > manual db changes, etc... and this always worked as expected too. > > Just to note - I do quick prototyping with sqlite but I switch to my final > db of choice as soon as possible, in order to properly set up indices, etc. > and test everything as extensively as possible. DAL is great, but there are > still differences between databases themselves and I wouldn't want to > discover an unexpected one on the last day of the project... > > Anyway, could you be more specific as to what's the current state of your > database and what would you like to achieve? Why did you need to use fake > migrations in the first place? I assume this is on web2py 2.2.1? > > Regards, > Ales > > > > > On Thursday, November 15, 2012 4:24:39 AM UTC+1, Richard Penman wrote: >> >> Having trouble migrating with postgres. >> >> With fake_migrate=True the the .table files are created. >> >> If migrate=True then error: auth_user already exists. >> >> Tried all combinations of these and deleting and removing .table files, >> but no joy. >> >> Is web2py meant to support modify the tables with postgres? If so which >> combination of options would you recommend? >> With sqlite this works fine. > > -- > > > --
