You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the ut_realtime_reporter is producing following output with disabled flag:
<test>
<disabled>true</disabled>
</test>
If test is not disabled we get the following outcome.
<test>
<disabled>false</disabled>
</test>
To keep backward compatibility we should not change that behaviour and add another flag.
I suggest introduction of <disabled_reason><![CDATA[Disabled reason description]]></disabled_reason>
I allowed myself to correct your post @jgebal as the word fale got me really confused :P
I totally agree that a new flag called disabled_reason would be best way.
I explained in utPLSQL/utPLSQL#1192 why I would use CamelCase and name the node disabledReason. IMO the next step is to implement the change outlined there.
Activity
jgebal commentedon Feb 7, 2022
Currently the
ut_realtime_reporteris producing following output with disabled flag:If test is not disabled we get the following outcome.
To keep backward compatibility we should not change that behaviour and add another flag.
I suggest introduction of
<disabled_reason><![CDATA[Disabled reason description]]></disabled_reason>So the results would be one of:
jgebal commentedon Feb 7, 2022
@simasch @lwasylow @PhilippSalvisberg
lwasylow commentedon Feb 7, 2022
I allowed myself to correct your post @jgebal as the word
falegot me really confused :PI totally agree that a new flag called
disabled_reasonwould be best way.PhilippSalvisberg commentedon Feb 25, 2022
I explained in utPLSQL/utPLSQL#1192 why I would use CamelCase and name the node
disabledReason. IMO the next step is to implement the change outlined there.PhilippSalvisberg commentedon Feb 27, 2022
Version 1.4.0 of the SQLDev extension can show the disabled reason. Here's a screenshot: