Skip to content

updateToMany/ToOne indexing.. #30

@dougsyer

Description

@dougsyer

One issue i've noticed with the updateToOne, updateToMany /utils methods is that if your relationships are created but the indexing fails for some reason during the modelling, it will never again try to update the componentsearch catalog and so you wont see the relation in the gui subcomponent.

Im assuming this is because changed_ids will be an empty set so the indexing will get skipped.

Im also assuming that this method does work when there are changes since I know its being used in the Netapp commercial zenpack and it looks to me like i can see all the to/many to/one rels there.

for now im assuming there is a bug somewhere in my modeller preventing the indexing but not the relations. or ive hacked up my dev environment indexing somehow.

but I do think that there should be a check somewhere to see if the relations match the componentsearch catalog so that you can survive a temporary indexing issue (ie zencatalogserver crash/reastart in enterprise, etc)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions