Re: dba_cons_columns table is messed up

but of course (grimace)

In article <38B3BDD8.3A45_at_yahoo.com>,
  connor_mcdonald_at_yahoo.com wrote:
> kal121_at_my-deja.com wrote:
> >
> > Anyone seen this strange behavior before? I'm getting back double
> > entries for the column names. I do not have this problem when I
query
> > user_cons_columns.
> >
> > > select column_name, constraint_name from dba_cons_columns where
> > table_name = 'LOGIN' order by constraint_name;
> >
> > COLUMN_NAME CONSTRAINT_NAME
> > ----------------- ------------------------------
> > CONTACT_ID FK_LOGIN_CONTACT
> > CONTACT_ID FK_LOGIN_CONTACT
> > LOGIN_ID PK_LOGIN
> > LOGIN_ID PK_LOGIN
> > LOGIN_ID SYS_C001078
> > CONTACT_ID SYS_C001079
> > USERNAME SYS_C001080
> > PASSWORD SYS_C001081
> > PASSWORD_HINT SYS_C001082
> > CREATED_BY_LOGIN SYS_C001083
> > CREATED_BY_ROLE SYS_C001084
> > DATE_CREATED SYS_C001085
> > LAST_LOGIN SYS_C001086
> > STATUS SYS_C001087
> > LOGIN_ID SYS_C00962
> > CONTACT_ID SYS_C00963
> > USERNAME SYS_C00964
> > PASSWORD SYS_C00965
> > PASSWORD_HINT SYS_C00966
> > CREATED_BY_LOGIN SYS_C00967
> > CREATED_BY_ROLE SYS_C00968
> > DATE_CREATED SYS_C00969
> > LAST_LOGIN SYS_C00970
> > STATUS SYS_C00971
> > USERNAME UQ_LOGIN
> > USERNAME UQ_LOGIN
> >
> > 26 rows selected.
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
> Include the OWNER in your query and see what happens...
>
> HTH
> --
> ===========================================
> Connor McDonald
> http://www.oracledba.co.uk
>
> We are born naked, wet and hungry...then things get worse
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Wed Feb 23 2000 - 13:42:05 CST