PSINDEXDEFN

Return to Index

This table corresponds to DBA_INDEXES. The specification of certain column attributes on PSRECFIELD implies the creation of certain indexes Additional indexes can then be specified in the Application Designer. Up to PeopleTools 7.x, PSINDEXDEFN and PSKEYDEFN were maintained for all record types, not just SQL tables, despite the fact that indexes cannot be built for the other object types, such as views! Indexes can be suppressed or enabled on either all or certain platforms. Thus PeopleSoft can deliver different indexes on different database platforms.

  • Parent record: PSRECDEFN
  • PSINDEXDEFNDBA_INDEXESDescription of PeopleTools Column
    PeopleSoft Field NameCorresponding Oracle Column Name
    RECNAMETABLE_NAMERecord (Table) Name, but not an exact match.
    (see PSRECDEFN.SQLTABLENAME)
    INDEXIDINDEX_NAMENot an exact match
    INDEX_NAME = 'PS'||INDEXID||RECNAME
    • _ = PeopleSoft Key Index. Implied from record definition.
    • 1-9 = Alternate Search Key Indexes. Implied from record definition.
    • (# = List Index. Implied from record definition. Only applicable in PeopleTools 7.5 and earlier, not used in PeopleTools 8)
    • A-Z = User Specified Index
    INDEXTYPE 
    • 1 = PeopleSoft Key Index
    • 2 = List Index
    • 3 = Alternate Search Key Index
    • 4 = User Specified Index
    UNIQUEFLAGUNIQUENESS
    • 1 = UNIQUE
    • 0 = NONUNIQUE
    CLUSTERFLAG No meaning in Oracle. A clustered index on SQL Server and Sybase is similar to an Index Organised Table in Oracle. This is not the same thing as an Oracle Clustered Index.
    ACTIVEFLAG 
    • 1 = Index to be built on at least one platform
    • 0 = Index not to be built on any platform
    CUSTKEYORDER 
    • 0 = Order of columns in PeopleTools generated index is the same as in the record
    • 1 = Developer specified order of columns in PeopleTools generated index.

    NB: Indexes with columns on a sub-record cannot have a custom key order.

    KEYCOUNT Number of columns in an PeopleTools index. A sub-record counts as one, so this does not correspond to the number of columns in the database index
    DDLCOUNT Number of distinct DDL override parameters specified on index across all platforms.
    PLATFORM_SBS 
    • 1 = Index to be built on SQL Base
    • 0 = Index not to be built on SQL Base

    Not used from PeopleTools 8. Database platform no longer supported.

    PLATFORM_DB2 
    • 1 = Index to be built on DB2
    • 0 = Index not to be built on DB2
    PLATFORM_ORA 
    • 1 = Index to be built on Oracle
    • 0 = Index not to be built on Oracle
    PLATFORM_INF 
    • 1 = Index to be built on Informix
    • 0 = Index not to be built on Informix
    PLATFORM_DBX 
    • 1 = Index to be built on DB2/Unix
    • 0 = Index not to be built on DB2/Unix
    PLATFORM_ALB 
    • 1 = Index to be built on AllBase
    • 0 = Index not to be built on AllBase

    Not used from PeopleTools 8. Database platform no longer supported.

    PLATFORM_SYB 
    • 1 = Index to be built on Sybase
    • 0 = Index not to be built on Sybase
    PLATFORM_MSS 
    • 1 = Index to be built on Microsoft SQL Server
    • 0 = Index not to be built on Microsoft SQL Server
    PLATFORM_DB4 
    • 1 = Index to be built on DB2/AS400
    • 0 = Index not to be built on DB2/AS400

    Not used from PeopleTools 8. Database platform no longer supported.

    IDXCOMMENTS Holds comment added by developer on user indexes only. Added in PeopleTools 8.4.

    Author: David Kurtz

    Return to Index

    © Go-Faster Consultancy Ltd.  Last updated 25 July 2010