Hi,

I just upgraded to the latest web2py version (1.92.1 source) in my 
development local win7 environment with postgresql and migrate=True, and my 
original problem occurred once again.

Traceback (most recent call last):
  File "C:\web2py\gluon\restricted.py", line 188, in restricted
    exec ccode in environment
  File "C:/web2py/applications/nube/models/model_06_tables_pre.py", line 87, 
in <module>
    dict(name='TEST'),
  File "C:/web2py/applications/nube/models/model_04_nube.py", line 327, in 
table
    self._table(xtable)
  File "C:/web2py/applications/nube/models/model_04_nube.py", line 289, in 
_table
    format=xtable.format)
  File "C:\web2py\gluon\dal.py", line 3500, in define_table
    polymodel=polymodel)
  File "C:\web2py\gluon\dal.py", line 541, in create_table
    self.create_sequence_and_triggers(query,table)
  File "C:\web2py\gluon\dal.py", line 1528, in create_sequence_and_triggers
    self.execute(query)
  File "C:\web2py\gluon\dal.py", line 1094, in execute
    return self.log_execute(*a, **b)
  File "C:\web2py\gluon\dal.py", line 1091, in log_execute
    return self.cursor.execute(*a,**b)
ProgrammingError: relation "xuser" already exists

<class 'psycopg2.ProgrammingError'>(relation "xuser" already exists)

(note that I'm using 'xuser' instead of 'auth_user')

My upgrade process consisted on the following simple steps:
  1. rename the previous web2py folder.
  2. install the new web2py version (hence the database folder is now 
empty).
  3. copy all my files (models, views, controllers, static) from previous 
version to new version.

And as soon as I try to open my app, I get the above error.

The only way I could solve it was to recreate the postgresql database.

I don't yet have a production system, but this problem scares me a lot when 
in a production system.

Should it have worked based on the upgrade steps I mentioned above?.

How can this issue be solved?.

Thanks again,

   Carlos

Reply via email to