Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#1533 closed enhancement (fixed)

Calendar doesn't work with PostgreSQL — at Version 3

Reported by: anonymous Owned by: Petr Machata
Priority: normal Component: CalendarPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10

Description (last modified by Alec Thomas)

Now when I add new event I see this error:

2007-05-12 21:06:18,108 Trac[main] ERROR: global name 'sqlite' is not defined
Traceback (most recent call last):
  File "K:\DevEnvironment\Python\Lib\site-packages\trac\web\main.py", line 387, in dispatch_request
    dispatcher.dispatch(req)
  File "K:\DevEnvironment\Python\Lib\site-packages\trac\web\main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "build\bdist.win32\egg\azcalendar\azcalendar.py", line 313, in process_request
  File "build\bdist.win32\egg\azcalendar\azcalendar.py", line 63, in process_add
  File "build\bdist.win32\egg\azcalendar\event.py", line 160, in save
NameError: global name 'sqlite' is not defined

It would be great if we could use calendar with PostgreSQL also

Change History (3)

comment:1 Changed 16 years ago by Igor

I've entered this bug, but forgot to eneter my email. Please, be free to send any questions to entered above email.

comment:2 Changed 16 years ago by Petr Machata

Resolution: fixed
Status: newclosed

We actually depend very little on particular SQL backend, only for error reporting. (SQL is hopefully generic enough.) When we reduce the amount of error reporting to mere "database failure", sqlite isn't required anymore. r2235 implements this, please go ahead and try if it does the job for you.

comment:3 Changed 16 years ago by Alec Thomas

Description: modified (diff)
Note: See TracTickets for help on using tickets.