Skip to content

Conversation

@imtbkcat
Copy link

TiDB use same error code to represent a class of code, like 8200 contain a series of error related to unsupported ddl. When using this terror lib, TiDB will panic. So, I remove this check.

Comment on lines 35 to 46
// CodeExecResultIsEmpty indicates execution result is empty.
CodeExecResultIsEmpty ErrCode = 3

// Expression error codes.

// CodeMissConnectionID indicates connection id is missing.
CodeMissConnectionID ErrCode = 1

// Special error codes.

// CodeResultUndetermined indicates the sql execution result is undetermined.
CodeResultUndetermined ErrCode = 2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do not add TiDB specific error to this lib. How about defining these code in TiDB?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

has been moved to TiDB, PTAL

@IANTHEREAL
Copy link

LGTM

@imtbkcat
Copy link
Author

imtbkcat commented Aug 3, 2020

PTAL @overvenus

@rleungx
Copy link
Member

rleungx commented Aug 4, 2020

Actually, it looks wired to import log related dependencies in common error repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants