At 05:30 PM 9/27/2002 +0300, Albert wrote:

[I tried to post on the new forum, but it failed]

Albert, please communicate with Patrick Barel <pbarel@...> about the problem you encountered.

Hi,

Lately, my test failed on eqQuery assertion. That's good.
But there is no way to see what data is actually different.

Is it possible to enhance eqQuery so that it prints out the actual differences it has found ?
I doubt, because in PL/SQL you cannot run dynamic select if you do not know exactly what columns it has.
Am I wrong ?

Dear Albert and others:

You are right. This is, I think, a tough one.

This same request came up when I visited Zurich and came across a project making extensive use of utPLSQL (which made me so happy). It is a very reasonable request, but I believe it is VERY challenging.

Right now, utPLSQL takes advantage of the MINUS SQL operator to cleanly tell us if there are differences. To figure out which row caused the problem and report on that, well, the dynamic SQL that is required frankly boggles my mind.

Perhaps others will be less boggled, so I hereby invite some smart and energetic person to take on this challenge: even if we just talk about it on this or soon the new forum, let's see if anyone has some really great ideas about how to "get granualar" with a dynamic query (how about DBMS_SQL.DESCRIBE_COLUMNS, for example?).

Thanks, SF