Details
There may be a need for a "multi-property" table column type. Such a
column type would create a single column that is comprised of data from
multiple entity properties. The motivating case is the "name"
column
type, which consists of last and first name.
A multi-property column type would allow the user to more intuitively
search across its constituent fields, and the filter UI that presents
such column types could present an appropriate, multi-field component.
Most importantly, a multi-property column type would be supported by
VirtualPagingDataModel, since DataEntityFetcher could now incorporate
the multiple fields into the generated "fetch keys" query.
(Currently,
the UserNameColumn restricts its search result to using only the
InMemoryDataModel, since its not possible to create a query for a column
that is derived from multiple database field). |
Details
There may be a need for a "multi-property" table column type. Such a
column type would create a single column that is comprised of data from
multiple entity properties. The motivating case is the "name"
column
type, which consists of last and first name.
A multi-property column type would allow the user to more intuitively
search across its constituent fields, and the filter UI that presents
such column types could present an appropriate, multi-field component.
Most importantly, a multi-property column type would be supported by
VirtualPagingDataModel, since DataEntityFetcher could now incorporate
the multiple fields into the generated "fetch keys" query.
(Currently,
the UserNameColumn restricts its search result to using only the
InMemoryDataModel, since its not possible to create a query for a column
that is derived from multiple database field). |