Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#3835 closed (fixed)

[boulder-oracle]: fails with TypeError

Reported by: frank.hoffsummer@… Owned by: adrian
Component: Core (Management commands) Version: other branch
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation:
Needs tests: Patch needs improvement:
Easy pickings: UI/UX:


Hello, I am on oracle-boulder-sprint branch r4815
trying to use ./ syncdb or ./ inspectdb on an empty oracle database fails now with the following exception:

Traceback (most recent call last):
  File "./", line 11, in ?
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/", line 1702, in execute_manager
    execute_from_command_line(action_mapping, argv)
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/", line 1602, in execute_from_command_line
    for line in action_mapping[action]():
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/", line 869, in inspectdb
    for table_name in introspection_module.get_table_list(cursor):
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/db/backends/oracle/", line 9, in get_table_list
    return [row[0].upper() for row in cursor]
TypeError: iteration over non-sequence

I could in an earlier revision use without getting this exception, so this must be new.
(the server is "Oracle 9i Enterprise Edition Release - 64bit Production" and I can connect fine to the database with sqlplus)

Change History (2)

comment:1 Changed 9 years ago by bouldersprinters

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

(In [4840]) boulder-oracle-sprint: Fixed #3835 by making CursorDebugWrapper
iterable, as it should have been.

comment:2 Changed 9 years ago by bouldersprinters

(In [4843]) boulder-oracle-sprint: Fixed #3820. See #3835 too, as this is a more
correct fix for the same issue (CursorDebugWrapper not iterable).

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