It's likely that some set of instructions related to SQL access via MySQLdb is causing Python to dump core. When Python dumps core, the zdaemon process restarts Zope, which is probably what you're seeing when you say it "starts a new process". It's possible that there is a library version mismatch in the code that you're using. If you continue to have problems, you should try to compile all the requisite C software (MySQLdb and MySQL) from source. Past that, I'm not sure I can help... you'll need to ask for support from the author of MySQLdb/MySQLDA. - C Peter de Jong wrote:

I installed the following stuff: ZMysqlda 2.06 mysql-python 0.3.5 Mysql 3.23.32

Peter de Jong

14-05-2001 13:27:39, "Chris McDonough" <chrism@digicool.com> schreef:

...

Hi Peter,

Which database adatper are you using?

- C

----- Original Message ----- From: "Peter de Jong" <p.dejong@melissendejong.nl> To: "Tino Wildenhain" <tino@wildenhain.de>; <zope@zope.org> Sent: Monday, May 14, 2001 1:07 PM Subject: Re: Exception from connection close was: Re: [Zope] (no subject)

...

Thak you for your reply,

I don't think this is the only problem; I am afraid that Zope on my machine is very instable; it starts an new process each time I try to change and test a sql-method (at least from a Opera-client; from Netscape changing an testing of the same method results in killing the server).

Hardly a robust platform.

I don't know what further to do.

sincerely Peter de Jong