public interface DBID extends DBIDRef, java.lang.Comparable<DBIDRef>, ArrayDBIDs, SetDBIDs
While this currently is just an Integer, it should be avoided to store the object IDs in regular integers to reduce problems if this API ever changes (for example if someone needs to do context tracking for debug purposes!)
In particular, a developer should not make any assumption of these IDs being consistent across multiple results/databases.
Modifier and Type | Method and Description |
---|---|
int |
compareTo(DBIDRef other)
Compare two DBIDs for ordering.
|
boolean |
equals(java.lang.Object obj)
Deprecated.
|
int |
hashCode()
In contrast to
DBIDRef , the DBID interface is supposed to have a
stable hash code. |
internalGetIndex
assignVar, binarySearch, get, iter, size, slice
int hashCode()
DBIDRef
, the DBID interface is supposed to have a
stable hash code. However, it is generally preferred to use optimized
storage classes instead of Java collections!@Deprecated boolean equals(java.lang.Object obj)
DBIDRef
, the DBID interface is supposed to have a
stable equals for other DBIDs.
Yet, DBIDUtil.equal(de.lmu.ifi.dbs.elki.database.ids.DBIDRef, de.lmu.ifi.dbs.elki.database.ids.DBIDRef)
is more type safe and explicit.
int compareTo(DBIDRef other)
Consider using DBIDUtil.compare(de.lmu.ifi.dbs.elki.database.ids.DBIDRef, de.lmu.ifi.dbs.elki.database.ids.DBIDRef)
, which is more explicit.
compareTo
in interface java.lang.Comparable<DBIDRef>
other
- Other DBID objectCopyright © 2019 ELKI Development Team. License information.