[Zope] ZMySQLDA and Zope 2.3.0

[Ron Bickers]

> -----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