EntityQuery exists fails with unknown column name

Problem/Motivation

Field definitions stating NULL as mainPropertyName produce a non-working query when using exists.

This leads to a failure when doing de/encrypt field configuration changes, and the entities are not queued for processing.

FE an address field, see the corresponding issue there #3250973: Compatibility With Entity Query Field Exists Method →

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'the_entity__field_entity_address.field_entity_address_' in 'where clause'

Steps to reproduce

- Add an address → field to a bundle.
- Change change the field's storage settings and enable encryption.

- Or an entity query for the entity type the bundle belongs to.
- And add $query->exists($field_name); to the query before running.

Proposed resolution

This should be addressed in core IMO. No issue yet.
The approach seems to be introducing a possibility to alter the entity query, see 📌 Add an alter hook to EntityQuery RTBC ,
which then would need to be implemented by a module using NULL as mainPropertyName.

Right now we can only provide a workaround ...