[Zope-DB] NotSupportedError - ZMySQLDA -- Help! ;-)

[Matthew T. Kromer]

OK, here's a good non-authoritative answer: contact the maintainer, Andy 
Dustman.  Its a judgement call as to whether or not the DA is correct 
raising a NotSupportedError -- in this case, it feels like the 
transaction is being rolled back by Zope, which might happen if you have 
a DTML error on a page which is unrelated to the database function.  The 
way I read the message, the database is warning you that some data you 
changed cannot be undone.
The DA shouldn't necessarily eat this, because it means the whole 
transaction couldn't be rolled back.

I'm not enough of a MySQL guy to know more about when it raises that 
particular error.

Chris Keyes wrote:

>When using ZMySQLDA to update a row in a table, we get the following error:
>
>Site Error
>An error was encountered while publishing this resource.
>
>_mysql_exceptions.NotSupportedError
>
>Sorry, a site error occurred.
>
>Traceback (innermost last):
>  File /usr/local/zope/2.4.0_base/lib/python/ZPublisher/Publish.py, line
>223, in publish_module
>  File /usr/local/zope/2.4.0_base/lib/python/ZPublisher/Publish.py, line
>179, in publish
>  File /usr/local/zope/2.4.0_base/lib/python/Zope/__init__.py, line 245, in
>abort
>  File /usr/local/zope/2.4.0_base/lib/python/ZODB/Transaction.py, line 179,
>in abort
>  File /usr/local/zope/2.4.0_base/lib/python/Shared/DC/ZRDB/TM.py, line 126,
>in abort
>  File /usr/local/hosting/accounts/hosting/Products/ZMySQLDA/db.py, line
>297, in _abort
>NotSupportedError: (1196, "Warning:  Some non-transactional changed tables
>couldn't be rolled back")
>
>The changes are correctly reflected in the database, however Zope raises
>this error. When tested using the ZSQL methods test function it completes
>correctly. Ideas??
>
>On the last line of the traceback, the line number 297 should be 296 but our
>print statement has raised the number.
>Zope is 2.4.0 and Python is 2.1. ZMySQLDA is 2.0.7.
>
>Thanks for your help
>Cheers
>
>ChrisK and HarryW
>