Re: [Tutor] inexplicable MySQLdb behavior, INSERT data doesn't appear

2005-04-20 Thread Liam Clarke
Seems a lot of wrappers are moving away from autocommit for performance reasons. pysqlite has removed it as of the alphra 2.0On 4/20/05, Danny Yoo <[EMAIL PROTECTED]> wrote: On Tue, 19 Apr 2005 [EMAIL PROTECTED] wrote:> hi all, while recently trying to insert some data into the following> table:>

Re: [Tutor] inexplicable MySQLdb behavior, INSERT data doesn't appear

2005-04-19 Thread Danny Yoo
On Tue, 19 Apr 2005 [EMAIL PROTECTED] wrote: > hi all, while recently trying to insert some data into the following > table: > > # stores unique course definitions > CREATE TABLE adminCourses ( > ID TINYINT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY, > Code CHAR(6), > Title VARCHAR(55), > Unit

Re: [Tutor] inexplicable MySQLdb behavior, INSERT data doesn't appear

2005-04-19 Thread Marilyn Davis
On Tue, 19 Apr 2005, Kent Johnson wrote: > Sounds like you need to commit() the initial cursor.execute() Yes. When we upgraded to 2.4, we had to add a commit(), so my own execute looks like: self.cursor.execute(this,args) did = self.connection.affected_rows() self.connection.commit() return di

Re: [Tutor] inexplicable MySQLdb behavior, INSERT data doesn't appear

2005-04-19 Thread Kent Johnson
Sounds like you need to commit() the initial cursor.execute() Kent [EMAIL PROTECTED] wrote: hi all, while recently trying to insert some data into the following table: # stores unique course definitions CREATE TABLE adminCourses ( ID TINYINT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY, Code CHAR(6

[Tutor] inexplicable MySQLdb behavior, INSERT data doesn't appear

2005-04-19 Thread tpc
hi all, while recently trying to insert some data into the following table: # stores unique course definitions CREATE TABLE adminCourses ( ID TINYINT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY, Code CHAR(6), Title VARCHAR(55), Units TINYINT UNSIGNED ) TYPE = InnoDB; I got a 1L value when I ran