Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AllowedChildTypes field is not indexed correctly #333

Closed
kavics opened this issue Apr 10, 2018 · 0 comments
Closed

AllowedChildTypes field is not indexed correctly #333

kavics opened this issue Apr 10, 2018 · 0 comments
Assignees
Labels
Milestone

Comments

@kavics
Copy link
Contributor

@kavics kavics commented Apr 10, 2018

This field writes terms like these:

  • sensenet.contentrepository.schema.contenttype[]
  • system.collections.generic.list`1[sensenet.contentrepository.schema.contenttype]

Expected: Discrete content type names.

Expected fixed fields:

  • AllowedChildTypes
  • EffectiveAllowedChildTypes

Investigation: these are handled by the AllowedChildTypesField that persists as a longtext field with NullFieldSetting that uses LowerStringIndexHandler.

@kavics kavics added this to the Sprint 156 milestone Apr 10, 2018
@kavics kavics self-assigned this Apr 10, 2018
@kavics kavics added the bug label Apr 10, 2018
@tusmester tusmester changed the title AllowedChildTypes is not indexed well AllowedChildTypes field is not indexed correctly Apr 10, 2018
@tusmester tusmester modified the milestones: Sprint 156, Sprint 157 Apr 18, 2018
@tusmester tusmester modified the milestones: Sprint 157, Sprint 158 May 2, 2018
@tusmester tusmester modified the milestones: Sprint 158, Sprint 159 May 16, 2018
@tusmester tusmester removed this from the Sprint 159 milestone May 29, 2018
@kavics kavics added the backend label Jan 16, 2020
@herflis herflis added this to the Sprint 202 milestone Jan 27, 2020
@tusmester tusmester closed this Feb 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.