| tags | displayed_sidebar | |
|---|---|---|
|
docsEnglish |
This page provides a list of error codes in ScalarDB SQL.
| Class | Description |
|---|---|
SQL-1xxxx |
Errors for the user error category |
Message
The namespace does not exist. Namespace: %sMessage
The table does not exist. Table: %sMessage
The column %s does not existMessage
The column does not exist. Table: %s; Column: %sMessage
The column index is out of bounds. Index: %d; Size: %dMessage
A positional bind marker is not allowed when binding named valuesMessage
A named bind marker is not allowed when binding positional valuesMessage
Cannot convert BLOB values to SQL. Please use a bind marker for a BLOB value and bind it separatelyMessage
No namespace name has been specified. Set a default namespace name, or explicitly specify a namespace nameMessage
Zero bytes may not occur in string parametersMessage
Mixing positional values and named values is not allowedMessage
Preparing a transaction is supported only in two-phase commit transaction modeMessage
Validating a transaction is supported only in two-phase commit transaction modeMessage
The previous transaction is still in progress. Commit, roll back, or suspend the previous transaction firstMessage
This SQL session has already been closedMessage
A transaction has not begunMessage
The type %s is not supportedMessage
No connection mode implementations are found. Please add a connection mode implementation to the classpathMessage
The connection mode is not specified, but multiple connection mode implementations are found. Specify one of the following connection modes: %sMessage
The connection mode '%s' is not found. Specify one of the following connection modes: %sMessage
Access denied: You need the %s privilege on the namespace %s to execute this operationMessage
Access denied: You need the %s privilege on the table %s to execute this operationMessage
Access denied: You can't grant the %s privilege because you don't have the same privilege on the table %sMessage
Access denied: You can't grant the %s privilege because you don't have the same privilege on the namespace %sMessage
Access denied: You can't revoke the %s privilege because you don't have the same privilege on the table %sMessage
Access denied: You can't revoke the %s privilege because you don't have the same privilege on the namespace %sMessage
Syntax error. Line %d:%d %sMessage
Syntax error. Multiple PRIMARY KEYs specified (exactly one required)Message
Cannot grant the INSERT privilege if the user doesn't have the UPDATE privilegeMessage
Cannot grant the UPDATE privilege if the user doesn't have the INSERT privilegeMessage
Cannot grant the UPDATE privilege if the user doesn't have the SELECT privilegeMessage
Cannot grant the DELETE privilege if the user doesn't have the SELECT privilegeMessage
Cannot revoke the SELECT privilege if the user has the UPDATE privilegeMessage
Cannot revoke the SELECT privilege if the user has the DELETE privilegeMessage
Cannot revoke the INSERT privilege if the user has the UPDATE privilegeMessage
Cannot revoke the UPDATE privilege if the user has the INSERT privilegeMessage
A non-clustering-key column is specified in the CLUSTERING ORDER directive. Column: %sMessage
The order of the columns in the CLUSTERING ORDER directive must match the order for the clustering key (%s must appear before %s)Message
The CLUSTERING ORDER is missing for the column %sMessage
Empty SQL is specifiedMessage
Multiple SQLs are not allowedMessage
The column %s is ambiguousMessage
The column %s cannot be specified in the %s clause. Only the columns in the table %s can be specified in the %s clauseMessage
An unbound bind marker is still in the escape character of the LIKE predicate for the column %sMessage
The escape character must be a TEXT value for the LIKE predicate for the column %sMessage
The value of the predicate must not be null unless the operator is 'IS NULL' or 'IS NOT NULL'. Predicate: %sMessage
An unbound bind marker is still in the LIMIT clauseMessage
The LIMIT must be an INT valueMessage
Unmatched column names or valuesMessage
The column %s is specified twiceMessage
All primary key columns must be specified in the INSERT or UPSERT statementMessage
An unbound bind marker is still in the value of the column %sMessage
Unmatched column type. The type of the column %s should be %s, but a boolean value (BOOLEAN) is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a decimal number (INT or BIGINT) is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a floating point number (FLOAT or DOUBLE) is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a string (TEXT) is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a BOOLEAN value is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but an INT value is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a BIGINT value is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a FLOAT value is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a DOUBLE value is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a TEXT value is specifiedMessage
Unmatched column type. The type of the column %s should be %s, but a BLOB value is specifiedMessage
RIGHT OUTER JOIN can only be specified as the first joinMessage
The JOIN predicate is not specified properly. Predicate: %sMessage
The data types of the columns in the JOIN predicate do not match. Predicate: %sMessage
The column %s is specified twice in the JOIN predicates. Predicates: %sMessage
Either all primary key columns or an indexed column for the table %s must be specified in the JOIN predicates. Predicates: %sMessage
Cannot issue mutation DML SQLs such as INSERT, UPDATE or DELETE with executeQuery()Message
Cannot issue SELECT SQLs with executeUpdate()Message
The TWO_PHASE_COMMIT_TRANSACTION mode is not supported in the current transaction managerMessage
The encrypted column %s is not allowed in the %s clauseMessage
The user %s does not exist