ephash not created in xntt_rest_queries table on install

Open on Drupal.org →

Created on 28 May 2025, 10 days ago

Problem/Motivation

I've got this php error in multiple places when attempting to inspect the connection or run a cron sync.

Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'q.ephash' in 'WHERE': SELECT "q"."qtimes" AS "qtimes" FROM "xntt_rest_queries" "q" WHERE "q"."ephash" = :db_condition_placeholder_0; Array ( [:db_condition_placeholder_0] => 776de0dfa8cd620a613154832f498904 ) in Drupal\external_entities\Plugin\ExternalEntities\StorageClient\RestClient->ensureQueryLimits() (line 44 of modules/contrib/external_entities/src/Plugin/ExternalEntities/StorageClient/QueryLimitationTrait.php).

It looks like a missing table column. On looking at the database, there is no ephash column in xntt_rest_queries. I tried creating it on my local and the API inspection completed without errors. It's not in the schema array in external_entities.install, should it be?

Steps to reproduce

1. Install the module.
2. Create a new REST external entity.
3. set values for "limit_qcount" and "limit_qtime" in the interface.
4. Inspect the connection.

Proposed resolution

Possibly define the ephash column in the xntt_rest_queries table in the hook_schema function in external_entities.install

Remaining tasks

User interface changes

None

API changes

Data model changes

🐛 Bug report

Status

Active

Version

3.0

Component

Code

Created by

🇳🇿New Zealand thomasmurphy

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @thomasmurphy
Comment 9 days ago →
🇳🇿New Zealand thomasmurphy
Comment 4 days ago →
🇫🇷France guignonv Montpellier
The fix seems correct so far, but I need to double check why the column was not there already. It was modified a long time ago (2-3 years I think) and I wonder if the fix is to add the column or remove the instructions using it.
Comment 1 day ago →
🇫🇷France guignonv Montpellier
guignonv → changed the visibility of the branch 3.0.x to hidden.
Comment 1 day ago →
🇫🇷France guignonv Montpellier
guignonv → changed the visibility of the branch 3.0.x to active.
Comment 1 day ago →
🇫🇷France guignonv Montpellier
You were right, the original schema was not updated! Only people with an old version that run update hook got the schema fixed. Thanks for the fix. I added the unique key constraint that was also missing in your patch (add it to your instance as well ;) ).

Please confirm it works for you now with this fix.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024