Modify

Opened 16 years ago

Closed 12 years ago

Last modified 12 years ago

#4118 closed defect (fixed)

PeerReview fails after install

Reported by: erne.castro@… Owned by: Ryan J Ollos
Priority: high Component: PeerReviewPlugin
Severity: critical Keywords:
Cc: erne.castro@…, Peter, Stjujsckij Nickolaj Trac Release: 0.11

Description (last modified by Ryan J Ollos)

After installing PeerReview plugin, both globally or local to a particular Trac environment, I can't use the plugin.

One clue: After installing, it didn't make me upgrade the environment.

The traceback is:

Python Traceback
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "build/bdist.linux-x86_64/egg/codereview/peerReviewMain.py", line 75, in process_request
  File "build/bdist.linux-x86_64/egg/codereview/dbBackend.py", line 38, in getMyCodeReviews
  File "build/bdist.linux-x86_64/egg/codereview/dbBackend.py", line 174, in execCodeReviewQuery
  File "/usr/lib/python2.5/site-packages/trac/db/util.py", line 51, in execute
    return self.cursor.execute(sql)
  File "/usr/lib/python2.5/site-packages/trac/db/util.py", line 51, in execute
    return self.cursor.execute(sql)
ProgrammingError: relation "codereviews" does not exist

Attachments (0)

Change History (14)

comment:1 Changed 16 years ago by anonymous

I have actually the same error:

relation "codereviews" does not exist

I did get a notification to upgrade the environment, this error was shown after the environment was upgraded.

Trac. 0.11.3

comment:2 in reply to:  1 Changed 16 years ago by Daniel Ziegenberg

Same to me.
Trac 0.12dev

comment:3 Changed 16 years ago by Daniel Ziegenberg

Priority: normalhigh
Severity: majorcritical

comment:4 Changed 15 years ago by Geoff Jacobs

presume this is related to #4698 have the same problem with 0.11

comment:5 Changed 15 years ago by Peter

Cc: Peter added
Trac Release: 0.100.11

Let me guess: this bug only manifests itself on Postgres backend. PeerReview plugin uses uppercase letters in it's tables and columns names, and for this to work on PG all names have to be double-quoted. Solution is to manually change all table & field names in DB to lowercase

comment:6 Changed 15 years ago by anonymous

I have the same problem, but when I upgrade environment I get a message:

Database is up to date, no upgrade necessary.

But Trac doesn't work and says that I have to upgrade environment. What to do?

comment:7 in reply to:  5 Changed 15 years ago by anonymous

Cc: Stjujsckij Nickolaj added

Replying to goldman:

Solution is to manually change all table & field names in DB to lowercase

Not manually though, see here.

Just remember not to use '\r' if you're running proper OS with '\n'-lineends

Nasty bug, though.

comment:8 Changed 14 years ago by anonymous

Another alternative is to change db_default.py prior to compiling / installing so each of the table and column names are lowercase.

comment:9 Changed 14 years ago by Ryan J Ollos

Description: modified (diff)

comment:10 Changed 14 years ago by Ryan J Ollos

Owner: changed from Sebastian Marek to Ryan J Ollos
Status: newassigned

comment:11 Changed 13 years ago by Marc

Owner: changed from Ryan J Ollos to Marc
Status: assignednew

comment:12 Changed 12 years ago by Ryan J Ollos

Owner: changed from Marc to Ryan J Ollos

This issue seems to be fixed on the trunk since proper use is now being made of the Trac API. Please reopen if you continue to have trouble with the latest trunk version.

comment:13 Changed 12 years ago by Ryan J Ollos

Resolution: fixed
Status: newclosed

comment:14 Changed 12 years ago by Ryan J Ollos

#4673 could be related.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ryan J Ollos.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.