On 2008-09-24 21:06, Bob Kline wrote: > Vernon Cole wrote: >> The column names are exactly what I asked for, but >> the order is all wrong. If I asked for row[1] I will get the wrong >> thing. If I could ask for row.displayName it would be correct. > > My first reaction when I read this was "surely the implementation of the > API is not behaving correctly"; but then I looked at what the > specification actually says, and indeed, there is no requirement that > the order of the tuples in the description sequence match the order of > the columns in the result set. Regardless of the merits of Vernon's > proposal (and I think his arguments have some validity), this seems like > a hole in the specification which should be addressed.
Agreed. Luckily implementors have done the right thing in the past 10 years or so :-) -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 24 2008) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ :::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
