Package: python-pymssql Version: 1.0.2+dfsg-1 Severity: normal Hi,
There seems to be a problem with the way pymssql sets Cursor.rowcount when running an UPDATE SQL query, consistently leaving it at 0. I believe PEP 249 says rowcount isn't strictly a MUST, but since the underlying _mssql library sets it correctly when using the execute_non_query method, it doesn't seem to be a design decision. In my superficial analysis of the code I noticed pymssql always calls execute_query regardless if it's a query or command (this seems to still be the case in the 1.9* dev version). Maybe some heuristics to determine the type of query would be enough to avoid this and call execute_non_query when appropriate? Or would that be a bit too naive? Cheers -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
