I have one application (called base) in which I define all the tables
for three other applications. In the three applications I use the same
db.py file. In these db.py files I set migrate=False on all tables.
One of these applications is a CMS, in which I enabled Authorization
and Authentication.
After upgrading debian to version 6, postgres was upgraded to 8.4. I
had to create a new user, new database. Well, this didn't go well.
I had previously backed up my database. Now after restoring my
postgres db, I had the error above.
"auth_user" already exists.
I have no idea how to fix th
To be clear, essentially this is what happened. I backed up web2py
folder, and postgres database separately. Then, I upgraded the os,
including postgres to version 8.4. After that, I unzipped the web2py
folder and installed the database.
And I have this problem.
This is quite frustrating. H
btw, I backed up (in postgres 8.3) using: "pg_dump database >
database.sql"
and restored (in postgres 8.4) using: "psql database < database.sql"
Just a guess, but did you back up the DB and then restore to a
different name?
It looks like web2py is trying to re-create the DB.
Try setting migrate = False, fake_migrate = True.
Look up those settings in the book, in the DAL chapter.
Regards, D
On Mar 20, 12:38 am, VP wrote:
> btw, I back
Yes. I've been able to "fixed" this, but it's ugly. I'm going to
create a new topic to describe this problem (this topic is convoluted
with many variables (upgrades, etc.)).
On Mar 19, 8:29 pm, villas wrote:
> Just a guess, but did you back up the DB and then restore to a
> different name?
>
>
6 matches
Mail list logo
