Re: UNION CASTING .

Hi!

I don't quite see the problem; your tables have NOT NULL and no one will be able to add inconsistent data in it, a view is basically a stored query, why bother with the constraints on a query?
Is this for documentation purpose?

If you had the situation below, how should the view be then? create table table1 (col1 integer NOT NULL) create table table2 (col1 integer NULL)
create view view1 as select * from table1 union all select * from table2

Frank!

Maze Control - Terminal 23315 - Central 2 <trw-sinterface_at_pluto.gwy> wrote in message news:0PbG6.12036$_W2.12062_at_news.indigo.ie...
> Can anyone help me with this ?
>
> Try the following SQL.
> --create table table1 (col1 integer not null)
> --create table table2 (col1 integer not null)
> --create view view1 as select * from table1
> ---union all select * from table2
>
>
>
> if you then do select column_name,nullable from user_tab_columns where
> table_name='VIEW1'
> the result is that col1 can contain nulls, which is incorrect.
>
> Try it on your own system - happens at least on Dynix and Win2000. V817
>
> Does anyone know how to hack the data dictionary to force this to be
> not-null ? (i.e. correct )
>
> Creating another view on top of this (AS SELECT COL1 from VIEW1 WHERE
 COL1
> is NOT NULL )
> does not work .
>
> This is a small case of a much larger production issue. The view cannot be
> replaced with a table.
> TIA !
>
>
>
Received on Fri Apr 27 2001 - 10:24:26 CDT