GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Failure when comparing nested objects · Issue #1082 · utPLSQL/utPLSQL Closed DescriptionDescribe the bug Provide version info Information about client software To Reproduce Run the below script create or replace type some_value as object( the_value number, is_relative integer(1) ); create or replace type some_item as object ( first_value some_value, second_value some_value ); declare l_expected some_item; l_actual some_item; begin l_expected := some_item(some_value( 1, 0 ), some_value(2.22, 1)); l_actual := some_item(some_value( 1, 0 ), some_value(2.22, 0)); ut.expect(anydata.convertObject(l_actual)).to_equal(anydata.convertObject(l_expected)); end; / See the exception: Expected behavior The expectation should report data differences. Additional context The behavior seem to show up when the object contains nested objects. Activity
|
| You are visitor 01402520 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |