Comments on Sydney Oracle Lab: Disabling specifc PL/SQL Warning messages

Thanks Gary - appreciate the response. I'll look ...

2010-01-14T20:13:51.451+11:00

Thanks Gary - appreciate the response.

I'll look out forthe full review of the book.

M.

You can compile specific objects with different le...

2010-01-14T14:06:39.832+11:00

You can compile specific objects with different levels of warning. I don't think it gets any lower level than that, or allows for any meta-data. Maybe something could be done with a database trigger, but that's not much better than comments.

ALTER PACKAGE test_warn compile plsql_warnings='ENABLE:ALL','DISABLE:07203';
Package altered.
ALTER PACKAGE test_warn compile plsql_warnings='DISABLE:ALL','ENABLE:07203';
SP2-0809: Package altered with compilation warnings

I'll do a fuller review of the book in a couple of weeks. The earlier part is fairly introductory so if you know PL/SQL it takes dedication to read it to pick up new details. The later part (security, performance, objects) is more interesting for me.

Hi Gary, This looks like the warning is disabled ...

2010-01-13T23:21:36.477+11:00

Hi Gary,

This looks like the warning is disabled for the entire session involved in the compile.

Are you aware of any means to disable the warning for a specific usage?

Let's say I have two warnings in a package and I only want to disable the warning for one of these usages.

Ideally, I'd like to add meta-data to the proc/function so that the compiler does not give a warning, and the next developer can see in the code that this is a deliberate usage.

Language supported meta-data would be a more robust means of achieving this rather than a comment, which is the fall back approach.

Are you happy with the new edition? Recommended? This one is on my reading list, but still looking for additional positive reviews.

Cheers,

Mathew Butler