org.knime.core.data
Interface BoundedValue
- All Superinterfaces:
- DataValue
- All Known Implementing Classes:
- BooleanCell, DateAndTimeCell, DoubleCell, IntCell, LongCell
public interface BoundedValue
- extends DataValue
A DataCell should implement this interface to indicate that its
objects can be reasonably ordered. "Reasonably" refers here to:
- There is more than just a trivial ordering (for instance lexicographical
ordering) defined for this cell type. Particularly, the preferred value
class of a DataCell (see here
for details) should expose a non-trivial comparator in its
DataValue.UtilityFactory.
- Determining the bounds of a table column whose
DataType is
compatible with this interface is desirable (see below).
This interface should be used, for instance for numeric data cells such as
DoubleCell or
IntCell, it should also be used for ordinal
columns (so far there is no ordinal column type in KNIME but if there were it
would implement this interface). On the other hand, types such as
StringCell or
ComplexNumberCell do not implement this
interface as they do not define a meaningful comparator.
Although not strictly enforced, a DataColumnSpec will have non-null
lower and upper bounds in its DataColumnDomain if the column's
DataType is compatible to this interface. It will typically not have
bounds for other types.
This interface does not specify any methods. It is only used to indicate the
above outlined property.
- Author:
- Bernd Wiswedel, University of Konstanz
Copyright, 2003 - 2012. All rights reserved.
University of Konstanz, Germany.
Chair for Bioinformatics and Information Mining, Prof. Dr. Michael R. Berthold.
You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, display, or in any way exploit any of the content, in whole or in part, except as otherwise expressly permitted in writing by the copyright owner or as specified in the license file distributed with this product.