[Zope] mysql trouble

[ghaley@mail.venaca.com]

there is something really funky with the new version of MySQLdb -- the
source of your error.  i ran into this exact same problem, then looked on
the site, and there was yet even a newer release.  it did not work either.  
track down a release of MySQLdb that came out in October or earlier,
delete the old package, and try it again.

by the way, once you get done installing it, you can test it from the
command line by typing python db.py all this does is establish the
database connection -- if it is working, it will return the command prompt
right away.  if it is broken, you will see an error trace that in my case
returned something along the lines that package Shared.DC.ZRDB.TM is
missing (or something).  even though in the lib/python/ directory, there
it is.  so, i trashed the most recent version, downloaded an older
version, and all is copasetic again.

i'm not sure about the mysql problem, if it is separate from the ZMySQL
problem.  i've run into a similar sort of problem, though.  mysql 3.23
uses a different architecture from 3.22  --  i recently migrated a bunch
of tables from a server running 3.22 to one running 3.23.  everything
moved fine except two tables, which are giving me an error message that
something did not translate.  i ended up dropping those tables and
rebuilding them.  not an easy task, since 3.23 has this wonderful feature
that allows you to write to an output file, which i could edit and then
use a load script on it to put the data in the new installation.

ciao!
greg.

> hi there,
> 
> after updating a SuSE 7.1 installation (mysql 3.22.32 to 3.32.30) i get the 
> error message at the bottom of this email.
> Zope 2.3.0 (binary release, python 1.5.2, linux2-x86) 
> ZMySQLDA-1-2-0 
> MySQLdb-0.1.2 
> 
> the crazy thing is, 
> 1. if i access the database with the mysql command line client i have no 
> trouble (about 200 rows) on both win and SuSE,
> 2. if i access the old database on a win system i can do that, but i 
> get no rows back (through the test tab)
> 3. if i downgrade the mysql on the SuSE system to the old one i have the same 
> trouble as in (2).
> 
> i also tried to upgrade to build MySQL-python-0.3.5 and get errors i have no 
> clue about what they are saying (on the bottom of this message.
> 
> i tried to fix this for about 100 hours over time and should really get that 
> fixed so help is very appreciated :-)
> 
> thanks in before
> 
> olaf
> 
> 
> error message
> ---------------------------------------
> Remarks for Errortracking
> 
> (Please pass this information to your support) 
> 
>       Error Type: BadRequest 
>       Error Value: Invalid connection string: ipOperate user password
>       Error URL: http://sino/ip/translations.db/manage_edit 
>       Error Message: Invalid connection string: ipOperate user password
>       Error Absolute URL: http://sino/ip/translations.db 
> 
>       The URL may be incorrect. 
>       The parameters passed to this resource may be incorrect. 
>       A resource that this resource relies on may be encountering an error. 
> 
> Traceback (innermost last):
>   File /home/soli-con/ipOffice/lib/python/ZPublisher/Publish.py, line 222, in 
> publish_module
>   File /home/soli-con/ipOffice/lib/python/ZPublisher/Publish.py, line 187, in 
> publish
>   File /home/soli-con/ipOffice/lib/python/Zope/__init__.py, line 221, in 
> zpublisher_exception_hook
>     (Object: RoleManager)
>   File /home/soli-con/ipOffice/lib/python/ZPublisher/Publish.py, line 171, in 
> publish
>   File /home/soli-con/ipOffice/lib/python/ZPublisher/mapply.py, line 160, in 
> mapply
>     (Object: manage_edit)
>   File /home/soli-con/ipOffice/lib/python/ZPublisher/Publish.py, line 112, in 
> call_object
>     (Object: manage_edit)
>   File /home/soli-con/ipOffice/lib/python/Shared/DC/ZRDB/Connection.py, line 
> 167, in manage_edit
>     (Object: RoleManager)
>   File /home/soli-con/ipOffice/lib/python/Shared/DC/ZRDB/Connection.py, line 
> 161, in edit
>     (Object: RoleManager)
>   File /home/soli-con/ipOffice/lib/python/Shared/DC/ZRDB/Connection.py, line 
> 240, in connect
>     (Object: RoleManager)
>   File /home/soli-con/ipOffice/lib/python/Products/ZMySQLDA/db.py, line 155, 
> in __init__
> BadRequest: (see above)
> 
> mysql-python 0.3.5 build log
> -------------------------------------------
> .py build
> running build
> running build_py
> not copying MySQLdb.py (output up-to-date)
> not copying CompatMysqldb.py (output up-to-date)
> not copying _mysql_const/__init__.py (output up-to-date)
> not copying _mysql_const/CR.py (output up-to-date)
> not copying _mysql_const/FIELD_TYPE.py (output up-to-date)
> not copying _mysql_const/ER.py (output up-to-date)
> not copying _mysql_const/FLAG.py (output up-to-date)
> not copying _mysql_const/REFRESH.py (output up-to-date)
> not copying _mysql_const/CLIENT.py (output up-to-date)
> running build_ext
> building '_mysql' extension
> gcc -O2 -m486 -fpic -I/usr/include/mysql -I/usr/include/python2.0 -c 
> _mysqlmodule.c -o build/temp.linux-i686-2.0/_mysqlmodule.o
> In file included from /usr/include/bits/posix1_lim.h:126,
>                  from /usr/include/limits.h:144,
>                  from 
> /usr/lib/gcc-lib/i486-suse-linux/2.95.2/include/limits.h:117,
>                  from 
> /usr/lib/gcc-lib/i486-suse-linux/2.95.2/include/syslimits.h:7,
>                  from 
> /usr/lib/gcc-lib/i486-suse-linux/2.95.2/include/limits.h:11,
>                  from /usr/include/python2.0/Python.h:27,
>                  from _mysqlmodule.c:29:
> /usr/include/bits/local_lim.h:36: linux/limits.h: Datei oder Verzeichnis 
> nicht gefunden
> In file included from /usr/include/errno.h:36,
>                  from /usr/include/python2.0/Python.h:48,
>                  from _mysqlmodule.c:29:
> /usr/include/bits/errno.h:25: linux/errno.h: Datei oder Verzeichnis nicht 
> gefunden
> error: command 'gcc' failed with exit status 1
> root@sino:/home/soli-con/ip-0.1.1/daten-import-p
> 
>