agesys-dev team mailing list archive

[Danny McRae <598414@xxxxxxxxxxxxxxxxxx>]

I encountered this problem also, however, when I built the package from
source instead of using the distributed binary, the problem went away.
One big clue as to where the problem may be is that I had to edit
setup.py to look for version 5.1 in the registry rather than version
5.0.

-- 
You received this bug notification because you are a member of Agesys
Team, which is subscribed to oursql.
https://bugs.launchpad.net/bugs/598414

Title:
  some problem in win32

Status in oursql:
  Triaged

Bug description:
  since 0.90 in windows, if i use execute() to search some data , when i
  fetch row i have get this exception :

  Traceback (most recent call last):
    File "<pyshell#12>", line 1, in <module>
      cur.fetchone()
    File "cursor.pyx", line 185, in oursql.Cursor.fetchone (oursqlx\oursql.c:16162)
    File "statement.pyx", line 422, in oursql._Statement.fetchone (oursqlx\oursql.c:10076)
    File "statement.pyx", line 234, in oursql._Statement._bind_buffer (oursqlx\oursql.c:8024)
    File "statement.pyx", line 126, in oursql._Statement._raise_error (oursqlx\oursql.c:6997)
  InterfaceError: (2036, 'Using unsupported buffer type: 3  (parameter: 3)', None)

  if i use oursql0.1 these is no problem, i dont know what happen