[Zope-DB] Keyword search broken after upgrade from 2.6.3 -> 2.7.0 ...

[Marc G. Fournier]

'k, we tried that ... switched 103 tables to innodb format, the error has 
now changed to:

------------
Zope Error

Zope has encountered an error while publishing this resource.

Error Type: RuntimeError
Error Value: external method could not be called because it is None

Troubleshooting Suggestions

     * 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.

For more detailed information about the error, please refer to the HTML source for this page.

If the error persists please contact the site maintainer. Thank you for your patience.
------------

Now, one thing I didn't note before, that I should have, sorry ... the 
section of hte site with the errors is the search section ... it has three 
"sub-sections" ... a keyword search (the above failure), a category search 
and a location search.  Both the category and location searches work 
perfectly fine, its only the keyword one that is failing ... if that means 
anything?



On Tue, 8 Jun 2004, Dieter Maurer wrote:

> Marc G. Fournier wrote at 2004-6-7 17:37 -0300:
>> Just finished going through the routine of upgrading a client from 2.6.3
>> -> 2.7.0 ... for the most part, it went uneventful, mostly had to do with
>> getting the proper modules installed for the MySQL backend ...
>>
>> But, they just found an error on their keyword search section of the site,
>> with the error generated being:
>> ...
>> NotSupportedError: (1196, "Warning: Some non-transactional changed tables couldn't be rolled back")
>
> Something generated an exception. This caused an abort
> of the Zope transaction. The "abort" was delegated to
> the "MySQL" connection which answered with a secondary exception:
> the one you see above.
>
> This is not a Zope 2.7 problem but one of your MySQL setup.
>
> Your options:
>
>  *  use only transaction capable tables in your MySQL database
>
>  *  tell the DA to ignore the exceptions above.
>     Beware! This can bring your MySQL in an inconsistent state
>
>  *  use a different database system with full transactional support
>
> --
> Dieter
>

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664