Aggregate funuctions broken in MySQLdb?

[Lorenzo]

In article <nnki629djmetubidlp82pcck1gadi3512p at 4ax.com>,
 Dennis Lee Bieber <wlfraed at ix.netcom.com> wrote:

> On Mon, 15 May 2006 20:14:29 GMT, John Salerno
> <johnjsal at NOSPAMgmail.com> declaimed the following in comp.lang.python:
> 
> > Lorenzo Thurman wrote:
> > > Thanks, that was my problem. Can you point me to some documentation on 
> > > MySQLdb? I've been googling to get answers and that obviously has not 
> > > been working.
> > 
> > I've been looking into this too lately, and finding thorough docs for it 
> > is hard. Have you seen these yet: 
> > http://sourceforge.net/docman/?group_id=22307
> 
> 	For the most part, it follows the DB-API 2 specifications. The
> subject of this thread (aggregates) would have occurred with ANY db-api
> compliant adapter, even plain ODBC -- since it was a misunderstanding
> that xxxx.execute() returns the status code (typically # of records
> affected by the query), and xxxx.fetchnnn() is needed to obtain the data
> values. This misunderstanding is not specific to use of aggregates as
> any "select..." statement functions this way.
> 
> 	Most divergences from the db-api specifications should be
> determinable by looking at the sources of the python portion of the
> adapter; or by looking at the features of the underlying RDBM.

Thanks, you are correct. I have done similar database things using PHP 
and Perl to connect to databases, and I felt like DUH, when I got my 
first reply, but there are times when one cannot see the forest for the 
trees, so to speak. Better docs can help.

-- 
"My Break-Dancing days are over, but there's always the Funky Chicken"
--The Full Monty