Toad 12.1 x64 (but affected all versions).
Here is example of constraint improvement that might help a lot…
Many Oracle users write create table statement like:
create table t (
COL1 NUMBER NOT NULL,
COL2 VARCHAR2(10 BYTE) NOT NULL
where constrained is automatically named by oracle.
When one compare such a table in two schemas, Toad report difference between them regarding this is, looking from Oracle perspective not true. The problem is that Toad compare constraints by name and not constrains by type and columns (what is in fact most important). Similar thing happened with automatic pk constraint which generate unique index by oracle name.
Now imagine several hundreds of tables and a result one might get with comparison.
So mine proposal for next versions is to implement logic which will be more intelligent in compare such a cases.