ZMySQLDA and Zope 2.3.0
Hi, I just wanted to mention that the new MySQL modules don't work with Zope 2.3. They seem to work (no broken Product. Open DB Connection) but then all SELECT statements return nonsense. I don't know if the problem is in the MySQLdb or the ZMySQLDA. Is there a list of the relevant changes in the API or data structures of Zope 2.3 besides the CHANGES.txt which lists only feature changes and fixes, AFAIK? --Oliver
Works for me. No Problems at all. ----- Original Message ----- From: "Oliver Frommel" <oliver@aec.at> To: <zope@zope.org> Sent: Wednesday, February 07, 2001 11:55 AM Subject: [Zope] ZMySQLDA and Zope 2.3.0
Hi,
I just wanted to mention that the new MySQL modules don't work with Zope 2.3. They seem to work (no broken Product. Open DB Connection) but then all SELECT statements return nonsense. I don't know if the problem is in the MySQLdb or the ZMySQLDA.
Is there a list of the relevant changes in the API or data structures of Zope 2.3 besides the CHANGES.txt which lists only feature changes and fixes, AFAIK?
--Oliver
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
I got the same problem with MySQLDA 1.2. So, I have switched to MySQLDA 2.0.4 and MySQLdb 3.0.2. Everything working now.... but I have to go to Python 2.0. With python 1.5.2 I have problems when sql tables has some int fields (it get followed by an L). On Wednesday 07 February 2001 09:55 am, you wrote:
Hi,
I just wanted to mention that the new MySQL modules don't work with Zope 2.3. They seem to work (no broken Product. Open DB Connection) but then all SELECT statements return nonsense. I don't know if the problem is in the MySQLdb or the ZMySQLDA.
Is there a list of the relevant changes in the API or data structures of Zope 2.3 besides the CHANGES.txt which lists only feature changes and fixes, AFAIK?
--Oliver
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Diego Rodrigo Neufert Webmaster / Web Developer - Magic Web Design ----------------------------------------------------------- diego@magicwebdesign.com.br www.magicwebdesign.com.br Curitiba - PR - Brasil
I got the same problem with MySQLDA 1.2.
So, I have switched to MySQLDA 2.0.4 and MySQLdb 3.0.2. Everything working now.... but I have to go to Python 2.0. With python 1.5.2 I have problems when sql tables has some int fields (it get followed by an L).
And I got this problem some time ago, when I tried to use MySQL functions like COUNT. I suppose that MySQL integers are much bigger than Pythons (about 11 bytes long; that seems to depend on the platform, too), so you get a long integer back (that's the L). I am not quite shure about all this, but declaring the integer-fields to be only 4 bytes long in MySQL, INT(4), solved the problem. Markus Kemmerling
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Markus Kemmerling Sent: Wednesday, February 07, 2001 8:51 AM To: Diego Rodrigo Neufert Cc: zope@zope.org Subject: RE: [Zope] ZMySQLDA and Zope 2.3.0
And I got this problem some time ago, when I tried to use MySQL functions like COUNT. I suppose that MySQL integers are much bigger than Pythons (about 11 bytes long; that seems to depend on the platform, too), so you get a long integer back (that's the L). I am not quite shure about all this, but declaring the integer-fields to be only 4 bytes long in MySQL, INT(4), solved the problem.
In ZMySQLDA 2.0.4, the MySQL INTEGER type was changed to use a Python long, because an unsigned integer can overflow a Python int. Because of this, you end up with the nastly little L at the end (using Python 1.5.2). If you use a smaller type in MySQL (as you did in your case), the DA uses a Python int so you don't end up with the L. _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
On Wednesday 07 February 2001 22:55, Oliver Frommel wrote:
Hi,
I just wanted to mention that the new MySQL modules don't work with Zope 2.3. They seem to work (no broken Product. Open DB Connection) but then all SELECT statements return nonsense. I don't know if the problem is in the MySQLdb or the ZMySQLDA.
Is there a list of the relevant changes in the API or data structures of Zope 2.3 besides the CHANGES.txt which lists only feature changes and fixes, AFAIK?
Well, I saw something like this when I moved to 2.3.0, and tried the new ZMySQLDA.... but I suspect it was because I didn't use the new Python module...
--Oliver
Have a better one, Curtis Maloney
participants (6)
-
Curtis Maloney -
Diego Rodrigo Neufert -
Markus Kemmerling -
Oliver Frommel -
Phil Harris -
Ron Bickers