| org.apache.derby.iapi.sql.execute.ExecIndexRow
All known Subclasses: org.apache.derby.impl.sql.execute.IndexRow, org.apache.derby.impl.sql.execute.IndexValueRow,
| ExecIndexRow | | public interface ExecIndexRow extends ExecRow(Code) | | This is an extension of ExecRow for use
with indexes and sorting.
author:
jeff after ames |
| Method Summary | |
| boolean | areNullsOrdered(int columnPosition)
Return true if orderedNulls was called on this ExecIndexRow for
the given column position. | | public void | execRowToExecIndexRow(ExecRow valueRow)
Turn the ExecRow into an ExecIndexRow. | | void | orderedNulls(int columnPosition)
These two methods are a sort of a hack. |
| areNullsOrdered | | boolean areNullsOrdered(int columnPosition)(Code) | | Return true if orderedNulls was called on this ExecIndexRow for
the given column position.
Parameters:
columnPosition - The position of the column (zero-based) forwhich we want to check if ordered null semanticsare used. true if we are to use ordered null semantics on the given column |
| execRowToExecIndexRow | | public void execRowToExecIndexRow(ExecRow valueRow)(Code) | | Turn the ExecRow into an ExecIndexRow.
|
| orderedNulls | | void orderedNulls(int columnPosition)(Code) | | These two methods are a sort of a hack. The store implements ordered
null semantics for start and stop positioning, which is correct for
IS NULL and incorrect for everything else. To work around this,
TableScanResultSet will check whether the start and stop positions
have NULL in any column position other than for an IS NULL check.
If so, it won't do the scan (that is, it will return no rows).
This method is to inform this ExecIndexRow (which can be used for
start and stop positioning) that the given column uses ordered null
semantics.
Parameters:
columnPosition - The position of the column that uses orderednull semantics (zero-based). |
|
|