[Sqlalchemy-tickets] [sqlalchemy] #2486: ResultProxy uses case-insensitive column names

[sqlalchemy <mi...@zz...>]

#2486: ResultProxy uses case-insensitive column names
------------------------+-----------------------------------------
 Reporter:  cdestigter  |           Owner:  zzzeek
     Type:  defect      |          Status:  new
 Priority:  medium      |       Milestone:
Component:  engine      |        Severity:  no triage selected yet
 Keywords:              |  Progress State:  awaiting triage
------------------------+-----------------------------------------
 We're dealing with tables with user-defined schemas. Sometimes they
 provide columns with duplicate names, except for case, e.g.:

 {{{
   CREATE TABLE foo ("bar" integer, "BAR" integer);
   INSERT INTO foo ("bar", "BAR") VALUES (1, 2);
 }}}

 While that's clearly crazy, I expect sqlalchemy to handle them.
 Unfortunately:

 {{{
   for row in table.select().execute():
     print row.items()
 }}}

 Causes:

 {{{
   Traceback (most recent call last):
     File "<ipython console>", line 4, in f
     File "/usr/lib/pymodules/python2.6/sqlalchemy/engine/base.py", line
 1359, in items
       return [(key, getattr(self, key)) for key in self.iterkeys()]
     File "/usr/lib/pymodules/python2.6/sqlalchemy/engine/base.py", line
 1352, in __getattr__
       return self.__parent._get_col(self.__row, name)
     File "/usr/lib/pymodules/python2.6/sqlalchemy/engine/base.py", line
 1620, in _get_col
       return processor(row[index])
     File "/usr/lib/pymodules/python2.6/sqlalchemy/engine/base.py", line
 1513, in process
       "try 'use_labels' option on select statement." % colname)
   InvalidRequestError: Ambiguous column name 'bar' in result set! try
 'use_labels' option on select statement.
 }}}

 The problem is apparent from the `ResultProxy` docstring:

 {{{
     Individual columns may be accessed by ... case-insensitive column name
 ...
 }}}

 Note that `row.keys()` and `list(row)` both work fine, so the exception
 message is actually misleading, because the fetch from the database works
 fine (the naming ambiguity is a problem in sqlalchemy, after the rows have
 been fetched)

 Discovered on 0.5.8 but that docstring is unchanged in the 0.7.7 source,
 so I assume it hasn't been fixed.

-- 
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2486>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python