You need to explain your question a little more clearly. Why would you need Global Variables in the where clause?
marist is right.
However, might I suggest that you store your variable in a table. In every database, I create an ApplicationValues_T table that looks like:
CREATE TABLE APPLICATIONVALUES_T (
APPLICATIONVALUES_ID NUMBER (1) NOT NULL,
NAME VARCHAR2 (30) NOT NULL,
DESCRIPTION VARCHAR2 (60),
STRING_VALUE VARCHAR2 (255),
NUMERIC_VALUE NUMBER (10),
Then, I can store any value that I need everywhere in this table. For example, this usually includes a database version (to be tested against the application version). You can use such a table to store your 'global' values and then include this table in your views.
I belive maxxx is talking about using global variables from PL/SQL package. If I'm mistaken ignore this message.
You can not reference package variables directly in a sql. But you can usePL/SQL function that returns the value of a package varible in the where clause of your wiev definition.
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
see sys_context and dbms_session.set_context if you are using oracle 8i.
Note: I am not very sure, whether it is applicable to your situation
Click Here to Expand Forum to Full Width