Thanks Matthew, that's done the trick. Okay, with that panic out of the way... Apologies for posting immediately instead of looking, but somebody is working on the Server at present, and will leave when I've run out of things for him to fix! Anyway, he's upgraded MySQL-3.23.33 (a tarball) to MySQL-3.23.47-1 (RPM). I wasn't expecting one of the features of such an upgrade to be the ommission of transaction support!!???!! He knows nothing of Zope (I'm working on him!!), and MySQL is working fine with my (previous) PHP apps, and now (with a - specified in the db connection string) with Zope... So, my next questions are... (1) what has happened? Where has transaction support gone? Is it an additional RPM I can install or something? (2) do I need it? my previous readings and your answer seem to suggest yes...!! Many thanks! Regards, Greg.

-----Original Message----- From: Matthew T. Kromer [mailto:matt@zope.com] Sent: 30 January 2002 20:55 To: Greg Conway Cc: Zope@Zope. Org Subject: Re: [Zope] transactions not supported by this server?

Greg Conway wrote:

...

Hi all,

I've just reinstalled MySQL, hopefully upping it to a later version, as I had some library problems (I have previously posted these, but have just managed to get it sorted!)

Now, my Zope site (previously working) comes up with the following:

Error Type: NotSupportedError Error Value: transactions not supported by this server

Can anybody please tell me what this means so I can fixed what worked five mins ago!!!!

thanks,

Greg Conway.

If I recall, the MySQL connect string is prefixed by an optional + or - to denote whether or not to connect to the server in transaction - enabled mode. Try putting a '-' in front of your connection string.

Note that this doesn't mean I recommend using a database without transaction support -- but you'll be working again.

*********************************************************************** This is a confidential communication between sender and addressee. If you are not the intended recipient of this message, please notify the sender and do not read, copy, use or disclose this communication to others. Any opinions or views expressed are those of the individual, and unless otherwise stated, are not those of the company. All attachments and intellectual rights remain the property of GML (NT) Limited. ***********************************************************************

On Wed, 2002-01-30 at 16:16, Greg Conway wrote:

Thanks Matthew, that's done the trick. Okay, with that panic out of the way...

Apologies for posting immediately instead of looking, but somebody is working on the Server at present, and will leave when I've run out of things for him to fix!

Anyway, he's upgraded MySQL-3.23.33 (a tarball) to MySQL-3.23.47-1 (RPM).

I wasn't expecting one of the features of such an upgrade to be the ommission of transaction support!!???!!

You need the MySQL-Max RPM for transaction support (in addition to the one you already have). However, if your application works without it, you aren't using transaction-safe tables to begin with, and so telling ZMySQLDA to use transactions is not helpful. If you convert your existing database over to use InnoDB tables or BDB tables, and install MySQL-Max, then transactions will mean something... -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net/andy You can have my keys when you pry them from my dead, cold neurons.