Contrib.social

No values saved to the target_id_int column

Open on Drupal.org →
Created on 1 April 2025, 5 days ago

Problem/Motivation

I have a custom entity with a DER field that allows nodes, media, and users. When I programticaly create an entity with

$my_entity = $this->entityTypeManager->getStorage('my_custom_entity')->create([
        'der_field' => $entity, // $entity is either a node, user, or media entity
      ]);
      $my_entity>save();

there is no value in the der_field_target_id_int column. However there is the correct value in der_field_target_id column.

I am sefining this field as a base field in my custom entity with

$fields['der_field'] = BaseFieldDefinition::create('dynamic_entity_reference')
      ->setLabel(t('My Field'))
      ->setDisplayOptions('view', [
        'label' => 'hidden',
        'weight' => 0,
      ])
      ->setSetting('exclude_entity_types', FALSE)
      ->setSetting('entity_type_ids', [
        'node' => 'node',
        'user' => 'user',
        'media' => 'media',
      ])
      ->setRequired(TRUE)
      ->setCardinality(1)
      ->setDisplayConfigurable('form', TRUE)
      ->setDisplayConfigurable('view', TRUE);

I also tried this and got the same results.

$my_entity = $this->entityTypeManager->getStorage('my_custom_entity')->create([
        'der_field' => [
          'target_id' => $content->id(),
          'target_id_int' => $content->id(),
          'target_type' => $content->getEntityTypeId(),
        ],
      ]);
      $my_entity>save();

Everything works except for the missing data in the int column.

Am I doing something wrong, or is this a bug?

🐛 Bug report
Status

Active

Version

4.0

Component

Code

Created by

🇺🇸United States loze Los Angeles

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @loze
  • Comment 5 days ago →
    🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

    Can you confirm you're running on a platform that lets you create triggers?
    The module relies on an SQL trigger to populate that column

  • Comment 5 days ago →
    🇺🇸United States loze Los Angeles

    Yes I am. So i reinstated my custom module and its working as expected now.

    However, on some DER fields that I created from the UI on another entity are doing the same thing now. This appears to have started after I did a config import drush cim. Could something have gone wrong there? is there anything I should look for that would indicate that?

  • Comment 5 days ago →
    🇺🇸United States loze Los Angeles
  • Comment 5 days ago →
    🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

    To be honest I wasn't involved in the trigger work and its been a headache since the get go.
    I'd be keen to explore doing it in something like a presave hook or onChange metrhod instead.

    I think you can run `SHOW TRIGGERS` and contrast that against the list of fields

  • Comment 5 days ago →
    🇺🇸United States loze Los Angeles

    ahh, my suspicion was correct.

    SHOW TRIGGERS FROM dbname;
    shows that the only triggers in this db are the one from the module i just reinstalled.

    I have a few other entities throughout this site that use DER fields.

    Is there a simple function I can call to recreate these missing triggers if I specify the field and entity type?

  • Comment 5 days ago →
    🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

    Looks like it happens in \Drupal\dynamic_entity_reference\EventSubscriber\FieldStorageSubscriber::getSubscribedEvents

    Which calls \Drupal\dynamic_entity_reference\Storage\IntColumnHandlerMySQL

  • Comment 5 days ago →
    🇺🇸United States loze Los Angeles

    Thank you for pointing me in the right direction @larowlan!

    After looking at what was going on there I was able to write my own function that added the missing triggers and everything appears to be working. Much appreciated.

    Now to just figure out how this happened in the first place.

  • Comment 5 days ago →
    🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

    No worries

    I'm keen to find some time to get rid of it because it prevents using the module on platforms that don't support triggers - Acquia being an example.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024