[issue5105] sqlite3.Row class, handling duplicate column names resulting from a SQL join

2009-02-05 Thread Georg Brandl
Changes by Georg Brandl ge...@python.org: -- resolution: - works for me status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5105 ___

[issue5105] sqlite3.Row class, handling duplicate column names resulting from a SQL join

2009-01-30 Thread Gabriel Genellina
Gabriel Genellina gagsl-...@yahoo.com.ar added the comment: I think this is a sqlite issue, not a Python one. cursor.description should return unique column names. -- nosy: +gagenellina ___ Python tracker rep...@bugs.python.org

[issue5105] sqlite3.Row class, handling duplicate column names resulting from a SQL join

2009-01-30 Thread Gabriel Genellina
Gabriel Genellina gagsl-...@yahoo.com.ar added the comment: See http://www.sqlite.org/cvstrac/tktview?tn=3221 Try upgrading to the latest sqlite release. Or set pragma full_column_names=ON; import sqlite3 conn = sqlite3.connect(':memory:') cursor = conn.cursor() cursor.execute(create table T

[issue5105] sqlite3.Row class, handling duplicate column names resulting from a SQL join

2009-01-30 Thread Brandon Adams
Brandon Adams sockonaf...@gmail.com added the comment: Ah, that's it. Thanks for the tip, this issue can be closed now. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5105 ___

[issue5105] sqlite3.Row class, handling duplicate column names resulting from a SQL join

2009-01-29 Thread Brandon Adams
New submission from Brandon Adams sockonaf...@gmail.com: When using sqlite3.Row as the row_factory for a sqlite3 connection and performing a SQL join that returns rows from two or more tables with identical column names, the returned sqlite3.Row object contains duplicate keys. Subsequently,