SMI table feature request
Posted in 1995
Topics: Storage & Space Management, Triggers, Constraints & Referential Integrity
I have found some deficiencies in the SMI tables for
which I have called in feature requests. I will summarize them
below. If you agree that these features are needed/useful,
I urge everyone to either call Informix giving verbal support
or send them email about it at tsmail@informix.com (technical
support address).
The more people requesting these, the more attention they will
get.
1. Request # 3926
The sysextents table needs to have at least a flag indicating
I for infex or T for table. When trying to use this table
to report on extents, the column called "tabname" may
also contain index names. When the index name is the same
as a table, you cannot tell which extents belong to the
table and which extents belong to the index.
Yea, I know I can get this from oncheck but I should also
be able to get it from these great SMI tables.
2. Request # 3713
Allow the leading column of a composite index to be
used for referential integrity. Right now, a separate
index is required only on that column. This is a bit
redundant.
3. Request # 3686
A new SMI table needs to be added that will bridge
systables with syschunks. It would very useful to
be able to report on tables and chunks using these
2 tables.
Thanks in advance for any support you can give to these.
Michael Reed, Radiix, Inc. - Informix OnLine consulting
3588 Plymouth Rd. Suite 257
Ann Arbor, MI 48105
voice: 313-677-UNIX, email: mreed@radiix.com