Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#16722 closed Bug (fixed)

import psycopg2.Error breaks psycopg2 backend

Reported by: Ubercore Owned by: anonymous
Component: Database layer (models, ORM) Version: master
Severity: Release blocker Keywords: psycopg2 Error postgresql import
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


The Error class doesn't need to be imported directly. Instead, Database.Error can be used.

Attachments (1)

psycopg2_import_error.diff (939 bytes) - added by Ubercore 3 years ago.

Download all attachments as: .zip

Change History (7)

Changed 3 years ago by Ubercore

comment:1 Changed 3 years ago by apollo13

  • Needs documentation unset
  • Needs tests unset
  • Owner changed from nobody to anonymous
  • Patch needs improvement unset
  • Status changed from new to assigned

+ a direct import seems to be impossible at all…

comment:2 Changed 3 years ago by apollo13

  • milestone set to 1.4

comment:3 Changed 3 years ago by Ubercore

  • Keywords psycopg2 Error postgresql import added

comment:4 Changed 3 years ago by anonymous

by removing the line 25, the django psycopg2 works again.
Sad to see that the SVN is not working tonight :(

comment:5 Changed 3 years ago by russellm

  • Resolution set to fixed
  • Status changed from assigned to closed

This has been resolved independently by [16710]

comment:6 Changed 3 years ago by jacob

  • milestone 1.4 deleted

Milestone 1.4 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

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

Note: See TracTickets for help on using tickets.