Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6414

MariaDB-specific SQLSTATE

        Details

        • Type: Task
        • Status: Closed
        • Priority: Major
        • Resolution: Won't Fix
        • Fix Version/s: N/A
        • Component/s: None
        • Labels:
          None

          Description

          Looking at this page:
          https://mariadb.com/kb/en/mariadb/mariadb-documentation/sql-language-structure/mariadb-error-codes/

          most errors seems to use the 'HY000' SQLSTATE, which is also used by several MySQL errors.

          I think it would be a bit more informative if such errors have a MariaDB-specific SQLSTATE. For two reasons:
          1) Applications and stored procedures which must handle them, will have a small hint.
          2) If MySQL will use your error codes in a future release, we can distinguish MariaDB errors using the SQLSTATE.

          In case you agree, I have a suggestion: 'MARIA' is a valid SQLSTATE

            Gliffy Diagrams

              Attachments

                Activity

                Hide
                Permalink
                serg Sergei Golubchik added a comment -

                Nice idea

                But that's generally not possible. Sqlstate values come directly from the SQL standard, it specifies exactly what every sqlstate means. HY000 is "general error" and we use it when no more specific sqlstate code is prescribed by the standard.

                Show
                serg Sergei Golubchik added a comment - Nice idea But that's generally not possible. Sqlstate values come directly from the SQL standard, it specifies exactly what every sqlstate means. HY000 is "general error" and we use it when no more specific sqlstate code is prescribed by the standard.

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    f_razzoli Federico Razzoli
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: