public static class DefaultComparisonUtilsTest.DatabaseObject extends AbstractDbObject
comparisonUtils| Constructor and Description |
|---|
DefaultComparisonUtilsTest.DatabaseObject(java.lang.String name) |
DefaultComparisonUtilsTest.DatabaseObject(java.lang.String name,
DbObject[] equivalentObjects) |
| Modifier and Type | Method and Description |
|---|---|
void |
accept(DbObjectVisitor visitor)
Allows a visitor to be invoked against this DbObject.
|
protected void |
doDiff(DbObject right,
DiffContext ctx)
Override this method to provide subclass specific diffing logic.
|
boolean |
sameAs(DbObject other)
Are the two
DbObjects logically the same? For example two Index objects may have
different names, but are the same index as they both index the same columns for the same table. |
diff, equals, getName, getParent, getTypeName, getValidators, hashCode, hasObjectLevelValidator, hasValidators, setComparisonUtils, setName, setParent, setValidators, toStringpublic DefaultComparisonUtilsTest.DatabaseObject(java.lang.String name)
public DefaultComparisonUtilsTest.DatabaseObject(java.lang.String name,
DbObject[] equivalentObjects)
public void accept(DbObjectVisitor visitor)
DbObjectprotected void doDiff(DbObject right, DiffContext ctx)
AbstractDbObjectdoDiff in class AbstractDbObjectpublic boolean sameAs(DbObject other)
DbObjectDbObjects logically the same? For example two Index objects may have
different names, but are the same index as they both index the same columns for the same table.
If two objects a and b have the same logical identity, it does not mean that a.equals(b) == true.
The two objects may well have differences and will be flagged as such by the schema comparison tool. When
a.sameAs(b) == true it makes it easier to show the differences as related, i.e. a and b are
different rather than, a is only in the 'left' tree and b is only in the 'right' tree.
sameAs in interface DbObjectsameAs in class AbstractDbObjectCopyright © 2005 - 2010 Alfresco Software, Inc. All Rights Reserved.