Compare Table Data bug?

Version 7.0.3.1123
I use the compare table data feature a lot to keep test and production databases in sync. However, I have just noticed that if I compare two tables where the difference is that one has a numeric column with 0 (zero) in it and one has null in it then it doesn't see this as being different. It works fine if they are varchar2 columns.
I can find no evidence of this bug anywhere.
Does anybody else have this problem?
 
Back
Top