As part of the process of making sure that null/not null constraints are consistent across development/staging/production, I'm looking at the dba_cons_columns table.
Now, as far as I know, column_names are limited to 30 characters, correct? If so, why is the column_name column in dba_cons_columns (9.2.0.1) a varchar2(4000)? I realize that the "extra space" isn't used and is never allocated so it's not like this is wasteful. But it's inconsistent with everything else, since dba_tab_columns has a column_name column of varchar2(30). anyone know why this is like this? Rachel __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Rachel Carmichael INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
