Code

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#3205 closed defect (fixed)

Postgresql bug introduced in rev 4244?

Reported by: jeffreyz@… Owned by: adrian
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: UI/UX:

Description

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/base.py ?). A summary of the error is:

   Request Method:  	POST
   Request URL: 	http://www.spor-development.vm.ntnu.no/spor/subscription/
   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/base.py 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.

Attachments (0)

Change History (2)

comment:1 Changed 7 years ago by adrian

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

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

comment:2 Changed 7 years ago by adrian

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

Add Comment

Modify Ticket

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


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

 
Note: See TracTickets for help on using tickets.