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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.