Hi,
I've installed Search API together with the Database search module as backend. Adding the server was unproblematic, but when I tried to configure a search index, I get the following exception every time I want to add or remove a field, or alter the type of a field:

DatabaseTransactionNoActiveException: in DatabaseConnection->popTransaction() (Zeile 1100 von xxx/includes/database/database.inc).

As I can see, a new table is created for every field I include in the index. So my conclusion is, that this error happens, when the Search API module does a CREATE, DROP or ALTER TABLE operation. I'm using MySQL version 5.1.43-nmm4-log

The good news is that the configuration is saved correctly and the DB tables are created / removed. And after running the indexing process, the indices in the DB tables seem to be filled correctly. So at this point - I haven't implemented the search function in the site so far - it seems that this error is just a bit annoying while configuring the search functionality, but does not block any functionality. So I stated this bug as minor.

I can remember that I've already tried Search API once a few months ago, on the same web hoster. I also immediately got this error message but I didn't have a closer look at this issue. I just removed the module and used the built-in search mechanism.

I'm also wondering that I haven't found an existing bug report about this issue. Am I really the only one who is experiencing this exception? Is the MySQL server configured exotically? Or have I done something wrong? I haven't found something special in the readme file, also my search index configuration is very basic and also happens if I just leave the title field or similiar fields.

Do you need further information? If yes, what?

Thanks for your answers,
Andi

Comments

drunken monkey’s picture

Status: Active » Fixed

Can't reproduce, but this is very probably related to #1007830: Nested transactions throw exceptions when they got out of scope. So a problem in core, little we can do about it here. (Maybe this is already fixed, though, so please also try the latest dev of core.)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.