René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Restricted columns in cursor compare","articleBody":"**Describe the bug**\r\nDue to the nature of cursor comparison implementation, when comparing cursor containing one of column names:\r\n- ITEM_DATA\r\n- DATA_ID\r\n- ITEM_NO\r\n- DUP_NO\r\n- POSITION\r\n\r\nThe cursor comparison fails.\r\n\r\n**Provide version info**\r\nutPLSQL v3.1.8\r\n\r\n\r\n**To Reproduce**\r\nThis can be observed on 3.1.8 with following block:\r\n```sql\r\nset serverout on\r\ndeclare\r\n  l_actual   sys_refcursor;\r\n  l_expected sys_refcursor;\r\nbegin\r\n  open l_actual   for select * from all_arguments where rownum = 1;\r\n  open l_expected for select * from all_arguments where rownum = 1;\r\n  ut.expect(l_actual).to_equal(l_expected);\r\nend;\r\n/\r\n```\r\n\r\n**Expected behavior**\r\n\r\nutPLSQL should not prevent column names that are commonly used / possible to use.\r\n\r\nOne idea would be to use quoted and more unusual names for internal columns in cursor compare: `\"UT3$_Item#Data\"`\r\n\r\n","author":{"url":"https://github.com/jgebal","@type":"Person","name":"jgebal"},"datePublished":"2019-09-22T01:32:43.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/997/utPLSQL/issues/997"}