Why can't constants of a package not be use in view definition?

Question

Hi,
maybe the answer is obvious, but I don't understand why this is not possible.
We have a large numer of key tables which define an ID-number (PK, generated by sequence), a short and long description as well as a numeric ID (AK1, in most cases autogenerated by max+1), which is intended for usage in programs, when a certain row of a key must be selected in the business layer. We call this column the type-ID of the key. A type-ID cannot be changed once assigned. Rows cannot be deleted physical, only logical (i.e. set column ACTIVE to FALSE).
We have a large numer of PL/SQL packages that use those type ID's. For every business object we define a globally available package that contains all necessary type ID's defined as constants, e.g.
create or replace package GLOBTEST is
CONST1 constant KEY_TABLE.TYPE_ID%type := 1;
end;
In all other packes we can use these constants (e.g. GLOBTEST.CONST1) instead of those "magic numbers". Now we have the situation that we must define quite a few views that must use those type IDs. But here we can't use these constants, e.g.
create or replace view V_TEST as
select GLOBTEST.CONST1 as CONST1 from DUAL;
results in error. What would be the best way to avoid using "magic constants"? We already defined functions which do nothing more than returning the appropriate constant. However we have the feeling that this is not the best way.
TIA,
Stefan
Message was edited by:
stefanm

Answer 1

Stefan,
You could try creating OBJECT views. I believe you would be able to call the constants already defined in packages in these object views. In the object views you can create member functions in case you want to do some manipulation of these constants or other data.
Shakti
http://www.impact-sol.com
Developers of Guggi Oracle - Tool for DBAs and Developers