Re: [sqlite] change after sqlite upgrade with python

2011-09-20 Thread Richard Hipp
On Mon, Sep 19, 2011 at 10:22 PM, Jamie Winquist wrote: > In my environment, we are connecting to the sqlite file using > pysqlite2.dbapi2. After upgrading from sqlite 3.5.4 to 3.7.7.1, iterating > over the results of a cursor.execute() are yielding different keys than they > did pre-upgrade. M

Re: [sqlite] change after sqlite upgrade with python

2011-09-20 Thread Simon Slavin
On 20 Sep 2011, at 3:22am, Jamie Winquist wrote: > After upgrading from sqlite 3.5.4 to 3.7.7.1, iterating over the results of a > cursor.execute() are yielding different keys than they did pre-upgrade. My > query is of the form: > > SELECT table.column1, table.column2 FROM table; Read the d

Re: [sqlite] change after sqlite upgrade with python

2011-09-20 Thread Stephan Beal
On Tue, Sep 20, 2011 at 4:22 AM, Jamie Winquist wrote: > With sqlite 3.5.4, when iterating over the cursor, the keys in each result > row were named "table.column1" and "table.column2" as specified in the > query. After the upgrade to sqlite 3.7.7.1, the keys in each result row do > not include