You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can now only use integers as id's for the search, if switched to strings we can use UUID's
Why?
When creating modules with Doctrine entities and UUID,
$id is char(36) in combination with (DC2Type:guid).
So using the current search module will not be possible anymore for these custom modules,
since it requires the $otherId to be an int and we have a char...
// save the tags
BackendSearchModel::saveIndex(string $module, int $otherId, array $fields, string $language = null)
The text was updated successfully, but these errors were encountered:
/** * @var string * * @ORM\Id() * @ORM\GeneratedValue(strategy="UUID") * @ORM\Column(type="guid") */private$id;
/** * @var int * * we need this since the search index only works with integers * * @ORM\Column(type="integer") */private$searchId;
/** * @param int $searchId * … */publicfunction __construct(
$searchId
…
) {
Type
Problem description
You can now only use integers as id's for the search, if switched to strings we can use UUID's
Why?
When creating modules with Doctrine entities and UUID,
$id is
char(36)
in combination with(DC2Type:guid)
.So using the current search module will not be possible anymore for these custom modules,
since it requires the $otherId to be an
int
and we have achar
...The text was updated successfully, but these errors were encountered: