GAUSS-01411 -- GAUSS-01420
GAUSS-01411: "cross-database references are not implemented: '%s.%s.%s'"
SQLSTATE: 0A000
Description: The SET CONSTRAINT statement is executed in the current database to set CONSTRAINT for another database.
Solution: Do not execute the SET CONSTRAINT statement in the current database to set CONSTRAINT for any other database.
GAUSS-01412: "constraint '%s' is not deferrable"
SQLSTATE: 42809
Description: The constraint in the SET CONSTRAINT statement is non-deferrable.
Solution: Do not set non-deferrable constraints as deferrable ones when executing the SET CONSTRAINT statement.
GAUSS-01413: "constraint '%s' does not exist"
SQLSTATE: 42704
Description: The constraint does not exist during SET CONSTRAINT statement execution.
Solution: Specify the constraint during SET CONSTRAINT statement execution.
GAUSS-01414: "no triggers found for constraint with OID %u"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-01415: "AfterTriggerSaveEvent() called outside of transaction"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-01416: "AfterTriggerSaveEvent() called outside of query"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-01417: "invalid after-trigger event code: %d"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-01418: "XC: Could not find the required row position %d for AFTER ROW trigger"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-01419: "XC: Could not find the required row position %d forAFTER ROW trigger"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-01420: "Partition column cannot be updated"
SQLSTATE: 42P10
Description: Distribution columns of the trigger function are being updated.
Solution: Do not update distribution columns.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot