Loading...

All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).

Ticket #121 (new enhancement)

Opened 10 years ago

Last modified 10 years ago

Topic name retrieval for topic hierarchies is very inefficient and not implemented in the TopicNode class yet

Reported by: andy@… Owned by: andy@…
Priority: minor Component: EasySearch
Keywords: Cc:

Description

When creating a hierarchical facet select that uses topics, it's very slow to retrieve the names in the demo as it calls dbo.epi_displayName for each topic individually through TMService.

Also, this has to be done in the search page as a XmlDocumentPostProcessors event, NOT through GetName on TopicNode which is not implemented yet.

A more efficient mechanism should be created, ideally one that can take a set of topic names and retrieve the localized name (with fallback support) as a single SQL call.

However, as a single level of the hierarchy typically contains <10 nodes, it's not really a major issue, just the first place to look if it runs slow and the first thing to fix!

Change History

comment:1 Changed 10 years ago by steve@…

  • Owner changed from steve@… to andy@…
  • Component changed from UnlistedComponent to EasySearch

Updating component.

Note: See HelpUser/Tickets for help on using tickets.