A quick heads up for anyone using r860 or beyond - it breaks any code which is
dependant on the order of values returned in a row, e.g. if you use a text
query, r = engine.execute('select foo, bar, baz from table',{}),fetchone() and
then expect that r[0] is foo's value, r[1] is bar's value and r[3] is baz's
value, your code will no longer work as adding more dictionary-like behaviour to
RowProxy has broken this. The fact is, RowProxy cannot implement all the traits
of a Python dictionary and preserve the order of column values at the same time,
so I will remove all the non-essential dictionary code from RowProxy (and write
some tests that check for preservation of column order). Hopefully, I haven't
caused anyone any grief (except myself) - I've been running lots of SQLAlchemy
code all day, importing a bunch of historic data and it wasn't until I ran some
of my more esoteric code that I found the problem.
Robert
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
