Re: Thanks, but... [2]

From: Piotr B. <piotrb_at_nie.spamuj.mnie>
Date: Fri, 28 Jan 2005 18:33:52 +0100
Message-ID: <ctdt8t$n3o$1@nemesis.news.tpi.pl>

Mark D Powell wrote:
> it may also be of interest that all_, dba_, and user_tab_columns
> contain a column named NULLABLE that can be used to
> determine the NULL allowed status of a column.

Yes, I mentioned this fact in my first post: > the information is already stored in user_tab_columns.nullable

Unfortunately, my problem remains unsolved. I want to write some application to export database schema from Oracle, and I don't see an easy way to distinguish "real", user-added check constraints (like "GENDER IN ('M', 'F')") from automatically generated and redundant "column IS NOT NULL" constraints for every non-null column.

Creating PL/SQL procedures/function to cast user_constraints.search_condition to varchar2 in order to apply "NOT LIKE '% IS NOT NULL'" is not possible when you have read-only access to the database... Received on Fri Jan 28 2005 - 11:33:52 CST