A bughunt just turned up a SELECT TOP without an ORDER BY inside a stored procedure. If it had (ever!) thrown an exception, it would have been dealt with an (embarrassingly!) long time ago.

Anyhoo... is there some way to turn warnings into exceptions inside a stored procedure in 12.0.1? e.g. SQLCODE 122 "The result returned is non-deterministic" http://dcx.sybase.com/index.html#1201/en/saerrors/err122.html

...not a local code change, but some setting that affects all the code... a local code change would imply the bug was suspected, and if the bug had been suspected it would have been hunted down and squashed.

asked 14 Oct '11, 07:55

Breck%20Carter's gravatar image

Breck Carter
27.4k424585837
accept rate: 21%

edited 14 Oct '11, 07:58

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×102

question asked: 14 Oct '11, 07:55

question was seen: 828 times

last updated: 14 Oct '11, 07:58