Title: Include the ability to handle PL/SQL exception variables in the %throws annotation · Issue #1234 · utPLSQL/utPLSQL · GitHub
Open Graph Title: Include the ability to handle PL/SQL exception variables in the %throws annotation · Issue #1234 · utPLSQL/utPLSQL
X Title: Include the ability to handle PL/SQL exception variables in the %throws annotation · Issue #1234 · utPLSQL/utPLSQL
Description: Within my internal PL/SQL subprograms, all errors are raised with exception variables. These exceptions are not linked to a specific error number until the exception is caught at the top level public PL/SQL procedure. This requires addit...
Open Graph Description: Within my internal PL/SQL subprograms, all errors are raised with exception variables. These exceptions are not linked to a specific error number until the exception is caught at the top level publ...
X Description: Within my internal PL/SQL subprograms, all errors are raised with exception variables. These exceptions are not linked to a specific error number until the exception is caught at the top level publ...
Opengraph URL: https://github.com/utPLSQL/utPLSQL/issues/1234
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Include the ability to handle PL/SQL exception variables in the %throws annotation","articleBody":"Within my internal PL/SQL subprograms, all errors are raised with exception variables. These exceptions are not linked to a specific error number until the exception is caught at the top level public PL/SQL procedure. This requires additional work to be done in the test code which hopefully could be done via the framework via the %throws annotation.\r\n\r\nI would like the ability to put a PL/SQL exception variable name (e.g. package and variable name of type exception) into the %throws annotation **without** the need to provide or associate a SQL error number using the PRAGMA EXCEPTION_INIT directive.\r\n","author":{"url":"https://github.com/markhawker76","@type":"Person","name":"markhawker76"},"datePublished":"2022-09-23T09:37:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/1234/utPLSQL/issues/1234"}| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:fd1f9464-fb39-2401-e077-303ab755b0ae |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 98D8:396977:16F1AC:1F7E46:6A616B7C |
| html-safe-nonce | e867188512723afb7eab8ab9ab2f532e50dff67985b61219fa4c6a1221145156 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5OEQ4OjM5Njk3NzoxNkYxQUM6MUY3RTQ2OjZBNjE2QjdDIiwidmlzaXRvcl9pZCI6IjQzNTEzNDEzMjkxMTUwODE1OTYiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | bbbe38ef259f91d0db7defa9aeb07097b08eafadcdb0b16d704966c5c994c438 |
| hovercard-subject-tag | issue:1383541340 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/utPLSQL/utPLSQL/1234/issue_layout |
| twitter:image | https://opengraph.githubassets.com/889ec8983d349b77fb4e4cf5613d1714a18413954c539dc734d13786ec922113/utPLSQL/utPLSQL/issues/1234 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/889ec8983d349b77fb4e4cf5613d1714a18413954c539dc734d13786ec922113/utPLSQL/utPLSQL/issues/1234 |
| og:image:alt | Within my internal PL/SQL subprograms, all errors are raised with exception variables. These exceptions are not linked to a specific error number until the exception is caught at the top level publ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | markhawker76 |
| hostname | github.com |
| expected-hostname | github.com |
| None | a69385f7d268ece7ad25b131bbd70f457024811fc79afcae43785a6849b724e2 |
| turbo-cache-control | no-preview |
| go-import | github.com/utPLSQL/utPLSQL git https://github.com/utPLSQL/utPLSQL.git |
| octolytics-dimension-user_id | 15661281 |
| octolytics-dimension-user_login | utPLSQL |
| octolytics-dimension-repository_id | 50728220 |
| octolytics-dimension-repository_nwo | utPLSQL/utPLSQL |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 50728220 |
| octolytics-dimension-repository_network_root_nwo | utPLSQL/utPLSQL |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 484cf265a1f970d5c7a5e7c37cb677d8010aa12f |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width