Good to know that the diff tag was useful. Simon (sjgibbs) was the originator of the diff feature request (Checking for consistency between systems thread).
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi Sujit,
Does diff work to compare the results between a store function that returns a ref cursor and a sql statement.
It will be of great help if it does.I tried and does not work.
can you give me any hint on this.
thanks a load in advance
Sathi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I dont think the diff tag does this. Basically, it matches the result of two <sql> or <call> elements. So if one of them sent out a REF CURSOR and the other was an SQL statement, then it would not work out of the box. One way to work around this is would be to create a generic Java program which returns a REF CURSOR given an SQL statement and use that instead of the SELECT itself. There is the <methodinvoker> tag that will allow you to run a Java program instead of <sql> or <call>.
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just had a requirement that I to compare data between multiple databases after running a form of synchronization / replication.
The diff tag appears to be just what the Dr. ordered.
Way to go SQLUnit!
Hi Dave,
Good to know that the diff tag was useful. Simon (sjgibbs) was the originator of the diff feature request (Checking for consistency between systems thread).
-sujit
hi Sujit,
Does diff work to compare the results between a store function that returns a ref cursor and a sql statement.
It will be of great help if it does.I tried and does not work.
can you give me any hint on this.
thanks a load in advance
Sathi
Hi Sathi,
I dont think the diff tag does this. Basically, it matches the result of two <sql> or <call> elements. So if one of them sent out a REF CURSOR and the other was an SQL statement, then it would not work out of the box. One way to work around this is would be to create a generic Java program which returns a REF CURSOR given an SQL statement and use that instead of the SELECT itself. There is the <methodinvoker> tag that will allow you to run a Java program instead of <sql> or <call>.
-sujit