Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#3205 closed defect (fixed)

Postgresql bug introduced in rev 4244?

Reported by: jeffreyz@… Owned by: Adrian Holovaty
Component: Database layer (models, ORM) Version: 0.95
Severity: critical Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I have encountered a runtime error when executing:

cursor.executemany( ... )

with a PostgreSQL 8.1 backend (psycopg 1 adaptor).

This error occurs with rev 4253 of django/trunk. I noticed that there was a recent change to the postgresql backend code in rev 4244, so I reverted to rev 4243. This fixed the problem, indicating that the bug may have been introduced in rev 4244 (in django/db/backends/postgresql/ ?). A summary of the error is:

   Request Method:  	POST
   Request URL:
   Exception Type: 	TypeError
   Exception Value: 	arg 2 must be a dictionary or tuple sequence
   Exception Location: 	/usr/lib/python2.4/site-packages/django/db/backends/postgresql/ in executemany, line 47

I will attach a copy of the web browser window to give the full details. As I am running on Linux, this will be a postscript file.

Change History (2)

comment:1 Changed 12 years ago by Adrian Holovaty

Resolution: fixed
Status: newclosed

(In [4257]) Fixed #3205 -- Fixed bug in custom postgresql executemany wrapper. Thanks for reporting, jeffreyz@…

comment:2 Changed 12 years ago by Adrian Holovaty

(I'm deleting the attachment because it may include sensitive data from your settings file.)

Note: See TracTickets for help on using tickets.
Back to Top