target_id_int is kept synchronized with target_id by a database trigger. Per
#3204103-12: Use virtual index instead of triggers →
, this is useful in case any code writes to the DER field's database tables directly, without going through Drupal's Entity API.Change DynamicEntityReferenceItem to also keep target_id_int in sync via Drupal. I think that all that needs to be done for this is:
DynamicEntityReferenceItem::schema() would need to add target_id_int as another column.DynamicEntityReferenceItem would need to override __get() such that when target_id_int is passed, it returns the integer value of target_id, otherwise call the parent getter.This could be in addition to leaving the existing trigger approach in place, so that sites where triggers are supported continue to get the benefit of the column staying synchronized even when target_id is updated in the database via something other than the Entity API. But this would enable sites where triggers aren't supported to also be able to use DER 4.x, so long as those sites don't update DER's database values without using the Entity API.
Needs work
4.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Has there been a resolution or change to this since 2022? I'm not certain, but we may have an issue with triggers as it relates to our hosting platform. I see a "failed testing" for most or all of the patches.
I'd say #3204103: Use virtual index instead of triggers → is the way forward here. I'm planning to work on it in a couple of weeks time.