Re[2]: [Zope-DB] rollback mysql?

[3205 5361 1215 9784]

Hello Juli=E1n,

Tuesday, August 6, 2002, 9:22:53 AM, you wrote:

JM> I think that zope is Rollbacking because there has been and error=
 in the
JM> current zope transaction.

    then how do i know what was the error inside zope? how could i ge=
t
    it printed out too?

JM> So this message is a warning: your database is going to be garbag=
ed.
JM> That's because some of your tables are not innodb (or another wit=
h
JM> transaction capability).

    i'll check that. so i should make them innodb?

JM> On Tue, 6 Aug 2002, 3205 5361 1215 9784 wrote:

>> Hello zope-db,
>>
>>   i have the following problem:
>>
>> =3D=3D=3D
>> Site Error
>> An error was encountered while publishing this resource.
>>
>> _mysql_exceptions.NotSupportedError
>>
>> Sorry, a site error occurred.
>>
>> Traceback (innermost last):
>>   File C:\www\notebook.hu\lib\python\ZPublisher\Publish.py, line 1=
50, in publish_module
>>   File C:\www\notebook.hu\lib\python\ZPublisher\Publish.py, line 1=
06, in publish
>>   File C:\www\notebook.hu\lib\python\Zope\__init__.py, line 178, i=
n abort
>>   File C:\www\notebook.hu\lib\python\ZODB\Transaction.py, line 107=
, in abort
>>   File C:\www\notebook.hu\lib\python\Shared\DC\ZRDB\TM.py, line 60=
, in abort
>>   File C:\www\notebook.hu\lib\python\Products\ZMySQLDA\db.py, line=
 328, in _abort
>> NotSupportedError: (1196, "Warning:  Some non-transactional change=
d tables couldn't be rolled back")
>> =3D=3D=3D
>>
>> mysql.log:
>>
>> 020806  8:27:41      76 Query       BEGIN
>>                      76 Query       update opt_cpu set
>>   opt_name=3D'IntelR Pentiumt-4',
>>   opt_short_name=3D'P4'
>>   where opt_id=3D13
>>                      76 Query       ROLLBACK
>>
>>
>>
>> why is zope rollbacking?
>> and whats all this?
>> the mysql has the correct new data, but zope gives an error...
>>
>> thanks,
>>
>>
>> k
>>
>>



--=20
don't believe everything you think