This simple database and table cause the problem for me. CREATE DATABASE IF NOT EXISTS `test` /*!40100 DEFAULT CHARACTER SET latin1 */; USE `test`; -- MySQL dump 10.13 Distrib 5.1.40, for Win32 (ia32) -- -- Host: localhost Database: test -- ------------------------------------------------------ -- Server version 5.1.44-community
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; -- -- Table structure for table `item_db` -- DROP TABLE IF EXISTS `item_db`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `item_db` ( `id` smallint(5) NOT NULL DEFAULT '0', `type1` tinyint(2) unsigned NOT NULL DEFAULT '0', `type2` tinyint(2) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `item_db` -- LOCK TABLES `item_db` WRITE; /*!40000 ALTER TABLE `item_db` DISABLE KEYS */; /*!40000 ALTER TABLE `item_db` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET time_zo...@old_time_zone */; /*!40101 SET sql_mo...@old_sql_mode */; /*!40014 SET foreign_key_chec...@old_foreign_key_checks */; /*!40014 SET unique_chec...@old_unique_checks */; /*!40101 SET character_set_clie...@old_character_set_client */; /*!40101 SET character_set_resul...@old_character_set_results */; /*!40101 SET collation_connecti...@old_collation_connection */; /*!40111 SET sql_not...@old_sql_notes */; -- Dump completed on 2010-07-25 23:25:50 -- some problem in win32 https://bugs.launchpad.net/bugs/598414 You received this bug notification because you are a member of Agesys Team, which is subscribed to oursql. Status in oursql python bindings for mysql: Incomplete 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 _______________________________________________ Mailing list: https://launchpad.net/~agesys-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~agesys-dev More help : https://help.launchpad.net/ListHelp
