kurt.forrester....@googlemail.com wrote:
> On Feb 3, 8:28 am, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote:
>> On Mon, 2 Feb 2009 23:28:05 -0800 (PST),
>> kurt.forrester....@googlemail.com declaimed the following in
>> comp.lang.python:
>>
>>> However, when I try to use the MySQLdb module it returns an incorrect
>>> value (it returns 1).
>>> I wish to use the DB API 2.0 compliant module for flexibility.
>>> Therefore I am trying to work out why the MySQLdb does not return the
>>> value as expected (that is as it is returned by the Query Browser).
>>> Any help would be greatly appreciated.
>> Show the code!
>>
>> At a rough guess, given the lack of details...
>>
>> You forgot to .fetch() the result and are looking at the status code
>> from the .execute()
>> --
>> Wulfraed Dennis Lee Bieber KD6MOG
>> wlfr...@ix.netcom.com wulfr...@bestiaria.com
>> HTTP://wlfraed.home.netcom.com/
>> (Bestiaria Support Staff: web-a...@bestiaria.com)
>> HTTP://www.bestiaria.com/
>
> Correct diagnosis.
>
> Thanks.
>
> Any ideas on how to suppress the warning output:
> __main__:1: Warning: No data - zero rows fetched, selected, or
> processed
> --
try:
...
except MySQLdb.Warning:
pass
There is probably some setting you can establish with MySQL so it
doesn't raise these warnings: I have never seen one, and zero rows is a
perfectly valid retrieval result.
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
--
http://mail.python.org/mailman/listinfo/python-list
