Class DDLSingleTableConstantAction

    • Field Detail

      • tableId

        protected UUID tableId
    • Constructor Detail

      • DDLSingleTableConstantAction

        DDLSingleTableConstantAction​(UUID tableId)
        constructor
        Parameters:
        tableId - the target table
    • Method Detail

      • dropConstraint

        void dropConstraint​(ConstraintDescriptor consDesc,
                            Activation activation,
                            LanguageConnectionContext lcc,
                            boolean clearDeps)
                     throws StandardException
        Drop the constraint corresponding to the received descriptor. If in doing so we also drop a backing conglomerate that is shared by other constraints/indexes, then we have to create a new conglomerate to fill the gap. This method exists here as a "utility" method for the various constant actions that may drop constraints in one way or another (there are several that do).
        Parameters:
        consDesc - ConstraintDescriptor for the constraint to drop
        activation - Activation used when creating a new backing index (if a new backing index is needed)
        lcc - LanguageConnectionContext used for dropping
        clearDeps - Whether or not to clear dependencies when dropping the constraint
        Throws:
        StandardException
      • dropConstraint

        void dropConstraint​(ConstraintDescriptor consDesc,
                            TableDescriptor skipCreate,
                            java.util.List<ConstantAction> newConglomActions,
                            Activation activation,
                            LanguageConnectionContext lcc,
                            boolean clearDeps)
                     throws StandardException
        See "dropConstraint(...") above.
        Parameters:
        newConglomActions - Optional List. If non-null then for each ConglomerateDescriptor for which we skip the "create new conglomerate" processing we will add a ConstantAction to this list. The constant action can then be executed later (esp. by the caller) to create the new conglomerate, if needed. If this argument is null and we skip creation of a new conglomerate, the new conglomerate is effectively ignored (which may be fine in some cases-- ex. when dropping a table).
        Throws:
        StandardException
      • dropConglomerate

        void dropConglomerate​(ConglomerateDescriptor congDesc,
                              TableDescriptor td,
                              Activation activation,
                              LanguageConnectionContext lcc)
                       throws StandardException
        Similar to dropConstraint(...) above, except this method drops a conglomerate directly instead of going through a ConstraintDescriptor.
        Parameters:
        congDesc - ConglomerateDescriptor for the conglom to drop
        td - TableDescriptor for the table on which congDesc exists
        activation - Activation used when creating a new backing index (if a new backing index is needed)
        lcc - LanguageConnectionContext used for dropping
        Throws:
        StandardException
      • dropConglomerate

        void dropConglomerate​(ConglomerateDescriptor congDesc,
                              TableDescriptor td,
                              boolean skipCreate,
                              java.util.List<ConstantAction> newConglomActions,
                              Activation activation,
                              LanguageConnectionContext lcc)
                       throws StandardException
        See "dropConglomerate(...)" above.
        Parameters:
        skipCreate - If true then we will skip the "create new conglomerate" processing for the dropped conglom.
        newConglomActions - Optional List. If non-null then for each ConglomerateDescriptor for which we skip the "create new conglomerate" processing we will add a ConstantAction to this list. The constant action can then be executed later (esp. by the caller) to create the new conglomerate, if needed. If this argument is null and we skip creation of a new conglomerate, the new conglomerate is effectively ignored (which may be fine in some cases-- ex. when dropping a table).
        Throws:
        StandardException
      • recreateUniqueConstraintBackingIndexAsUniqueWhenNotNull

        void recreateUniqueConstraintBackingIndexAsUniqueWhenNotNull​(ConglomerateDescriptor cd,
                                                                     TableDescriptor td,
                                                                     Activation activation,
                                                                     LanguageConnectionContext lcc)
                                                              throws StandardException
        Recreate backing index of unique constraint. It first drops the existing index and creates it again with uniqueness set to false and uniqueWhenNotNull set to true. It reuses the uuid so there is no need to update ConstraintDescriptor.
        Parameters:
        cd - ConglomerateDescritor to recreate
        td - TableDescriptor for table on which congDesc exists
        activation - Activation used when creating a new backing index (if a new backing index is needed)
        lcc - LanguageConnectionContext used for dropping
        Throws:
        StandardException
      • getConglomReplacementAction

        ConstantAction getConglomReplacementAction​(ConglomerateDescriptor srcCD,
                                                   TableDescriptor td,
                                                   java.util.Properties properties)
                                            throws StandardException
        Create a ConstantAction which, when executed, will create a new conglomerate whose attributes match those of the received ConglomerateDescriptor.
        Parameters:
        srcCD - Descriptor describing what the replacement physical conglomerate should look like
        td - Table descriptor for the table to which srcCD belongs
        properties - Properties from the old (dropped) conglom that should be "forwarded" to the new (replacement) conglom.
        Throws:
        StandardException
      • executeConglomReplacement

        void executeConglomReplacement​(ConstantAction replaceConglom,
                                       Activation activation)
                                throws StandardException
        Execute the received ConstantAction, which will create a new physical conglomerate (or find an existing physical conglomerate that is "sharable") to replace some dropped physical conglomerate. Then find any conglomerate descriptors which still reference the dropped physical conglomerate and update them all to have a conglomerate number that points to the conglomerate created by the ConstantAction. This method is called as part of DROP processing to handle cases where a physical conglomerate that was shared by multiple descriptors is dropped--in which case a new physical conglomerate must be created to support the remaining descriptors.
        Parameters:
        replaceConglom - Constant action which, when executed, will either create a new conglomerate or find an existing one that satisfies the ConstantAction's requirements.
        activation - Activation used when creating the conglom
        Throws:
        StandardException