28. Error codes

Every error that MIRAJ returns carries three pieces of information: a numeric code, a 5-character SQLSTATE and a message in the server language. This page lists the numeric codes that the engine produces, with their SQLSTATE and the exact French wording of the message, together with an explanation of the typical cause and, where useful, a suggested fix.

1. How to read a MIRAJ error#

An error returned by the engine or by the network server looks like this:

ERROR 1146 (42S02): La table 'ventes.clients' n'existe pas

(This is how the miraj-cli console presents it in French; other clients write ERROR 1146 (42S02): ….)

• 1146 is the numeric code, specific to MIRAJ (taken from a well-established historical numbering in the SQL ecosystem, so as to remain familiar to existing tools);
• 42S02 is the SQLSTATE, an engine-independent standard (see §3);
• the text is the message, produced from a template in which the %s placeholders have been replaced by the values of the error (table name, column name, etc.).

A warning (level Warning or Note) also carries a code from this page; the statement succeeds and SHOW WARNINGS lists it:

SELECT CAST('abc' AS SIGNED);
SHOW WARNINGS;

+-----------------------+
| CAST('abc' AS SIGNED) |
+-----------------------+
|                     0 |
+-----------------------+

+---------+------+------------------------------------------+
| Level   | Code | Message                                  |
+---------+------+------------------------------------------+
| Warning | 1292 | Truncated incorrect INTEGER value: 'abc' |
+---------+------+------------------------------------------+

2. Error code reference table#

The French message is given word for word (%s = value substituted at runtime: table name, column name, etc.).

2.1 Syntax and parsing errors#

2.2 Schema errors (databases, tables, columns, indexes)#

2.3 Constraint and data errors#

2.4 Privilege errors#

2.5 Transaction and concurrency errors#

2.6 Cluster and replication errors (Cluster edition)#

2.6 bis Binary log and binary-log replication errors#

2.7 MIRAJ-specific errors (editions, change events and vectors)#

These codes exist in no other SQL engine; they are specific to MIRAJ.

2.8 Internal and miscellaneous errors#

2.9 Stored program errors (procedures, functions, triggers, events)#

3. The SQLSTATE#

The SQLSTATE is a code of exactly 5 characters (digits and uppercase letters), standardized independently of MIRAJ and shared by most SQL engines. An application can rely on it for generic handling, without knowing the wording or even the MIRAJ-specific numeric code — useful when porting code written against another SQL engine.

A few classes worth knowing:

Recommended usage on the application side: a driver (ODBC, JDBC, ADO.NET...) generally exposes the SQLSTATE alongside the native code. For portable handling across engines (retrying a transaction on 40001, distinguishing a 23000 constraint error from a 42000 syntax error), rely on the SQLSTATE. For precise MIRAJ-specific diagnosis (displaying a suitable message, distinguishing two causes that share the same SQLSTATE), rely on the numeric code from this page.

When no more specific SQLSTATE is defined for a code, MIRAJ returns HY000 by default (including for a code entirely unknown to the catalog).

An error raised by a stored routine with SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = '...' carries the SQLSTATE chosen by the routine rather than the one associated with the generic numeric code of SIGNAL — this is the normal mechanism for raising an application error with a custom SQLSTATE (class 45 reserved for this use).

3.1 PostgreSQL-language instance#

On an instance in the PostgreSQL language (§ 16.10, chapter 30), the client receives only the SQLSTATE and the message: the codes that PostgreSQL drivers recognize replace the generic SQLSTATE of the MIRAJ code.

4. Message language#

MIRAJ error messages exist in several languages: French, English, and eight additional languages (Chinese, Hindi, Spanish, Arabic, Portuguese, Russian, German, Japanese). This page documents the French wording, the reference language of this manual.

To obtain the messages in English (or in another available language):

• the --lang option of miraj-server (en, fr, zh, hi, es, ar, pt, ru, de, ja), or of miraj-cli opened on a data folder, selects the language of error messages and warnings (SHOW WARNINGS, MIRAJ language: Données tronquées pour la colonne 'v' à la ligne 1 for 1265 in French); in the MIRAJ language, the warnings and notes listed by SHOW WARNINGS are written in the same language as the errors (for example, under --lang fr, Warning | 1265 | Données tronquées pour la colonne 'v' à la ligne 1), their code remaining the same;
• each error can also be reworded in a given language without changing the session language, if the API or tool used exposes this feature (on-demand retranslation from the error's code and arguments);
• <language>.json files placed next to the server executable allow you to complete or replace the embedded translations, including to add a language not listed above.

The numeric code and the SQLSTATE of an error never change with the language: only the message text is translated. An application that tests the code or the SQLSTATE (rather than the message text) therefore works identically regardless of the language configured on the server.