Ticket #264 (closed Enhancement: fixed)
Core: the (calculated) value of composite topics should be indexed
| Reported by: | jri | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.1 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.0.11 |
| Keywords: | Cc: | dgf | |
| Complexity: | 3 | Area: | Application Framework / API |
| Module: | deepamehta-core |
Description
Currently only simple topic values are indexed
Change History
comment:2 Changed 12 years ago by Jörg Richter
- Status changed from accepted to closed
- Resolution set to fixed
Core: index composite values (#264).
In your model you can set index modes for composite types just as you do for simple types.
Note: as I've just recognized this functionality was there already but not used in any model.
2 composite values of the Contacts model are now indexed:
dm4.contacts.person_name
dm4.contacts.address
In both cases index mode "dm4.core.fulltext_key" is used, so these fields should be ready for auto-completion.
IMPORTANT: in order to deploy the new Contacts model you must reset the DB.
Close ticket 264.
comment:3 Changed 12 years ago by Jörg Richter
Core: index composite values (#264).
In your model you can set index modes for composite types just as you do for simple types.
Note: as I've just recognized this functionality was there already but not used in any model.
2 composite values of the Contacts model are now indexed:
dm4.contacts.person_name
dm4.contacts.address
In both cases index mode "dm4.core.fulltext_key" is used, so these fields should be ready for auto-completion.
IMPORTANT: in order to deploy the new Contacts model you must reset the DB.
Close ticket 264.
