Somehow the search_api update returned that error for me:

    * Failed: PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.status' in 'field list': SELECT base.id AS id, base.type AS type, base.label AS label, base.weight AS weight, base.data AS data, base.status AS status, base.module AS module FROM {profile_type} base; Array ( ) in EntityAPIController->query() (line 153 of /var/www/fago/web/recruiter/profiles/recruiter/modules/entity/includes/entity.controller.inc).

Don't know what it does with profiles, but I guess the update somehow triggered indexing of profiles.

So I had a short look at search API updates and noted they make use of some API functions, e.g. for entity loading. But they shouldn't, as your API functions cannot be expected to work during updates (as my case demonstrates). Even worse, at some point in future they might not be available any more, e.g. when updating a d7 install to d9.

So best, just use low-level stuff like db-tng variable_get/set only.

CommentFileSizeAuthor
#1 search_api_updates.patch1.47 KBfago
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

fago’s picture

Status: Active » Needs review
FileSize
1.47 KB

Attached patch fixed the last update for me. Also, fixed the comment to not exceed 80 characters per line.

drunken monkey’s picture

Title: updates may not call API functions » Updates must not call API functions
Status: Needs review » Fixed

Oh, sorry, I read somewhere in a core issues that non-doc-comments are allowed to span multiple lines. Either that was wrong, or has changed … In any case, thanks for noting that!

And of course also thanks for the patch, I committed it now. Sorry for using API functions, I'll (try to) avoid them in the future!

fago’s picture

Only the first line of a doc-block comment is allowed to exceed 80 chars in order to be a full sentence. Else, the 80 char rule applies.

Status: Fixed » Closed (fixed)

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