Hi Norm,
In reply to: Norm [TeamT] wrote the following post at 21 Apr 2017 11:53 AM:
That was it...you nailed it! There was no query, just a partial listing of columns. I changed vSQL to Clob, [you even left a comment in there "Change the size if something barfs!", which I had not noticed earlier].
For 'H91A', in my test sandbox environment, your code found (14) places. By comparison, the modified Tom Kyte Anonymous Block code, which I already had determined was not looking for additional columns in a table once a match was found, located (11) tables. Of the (14) results your code located, three tables had two columns each with the same data. As you can see, Norm, there are NormALIZATION issues that we deal with. Sorry, that stupid pun just came to mind! [H]
A few more questions, if I may...
- In debug mode for your NormSearch procedure, what determines the order that the columns were printed (and presumably interrogated in the database)? It was neither alphabetical nor by ordinal number.
- Is there an easy way to add a comment to the end of the query string that indicates the ordinal position for the column? For example:
select * from "TGW7078"."AW_WORK_STATEMENT_AIRPLANE" where "TPRN_COMMENTS" like '%H91A%'; -- Column 49
select * from "TGW7078"."AW_WORK_STATEMENT_AIRPLANE" where "WORK_STATEMENT" like '%H91A%'; -- Column 7
Now, if I can just convince the IT Powers-to-be, at this little airplane company, that a "one-offs" collection of procedures in production would be useful to us.....
Tom