I encountered the following incompatibility problem.
I developed some Python scripts, which access a MySQL database using the MySQLdb module.
The environment was RedHat 8.0, and the MySQLdb RPM version was 0.9.1-4.
Now, I am trying to run the same scripts in Debian Sarge environment, and the MySQLdb package version is now 1.1.6-1.
I found that the old MySQLdb returned string fields as Python strings.
The new MySQLdb returns them as array.ArrayType objects (for example, string 'incompatible' is now returned as array.array('c','incompatible')).
Thus, I have to modify my scripts at several types to convert the array.ArrayType back into string (using the tostring() function).
Does anyone know about this change in the API?
Is there any way to configure the MySQLdb cursor being used to return strings as strings rather than as array.ArrayType objects, so that I'll not have to modify my scripts at several places?
--- Omer
My own blog is at http://www.livejournal.com/users/tddpirate/
My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
