SQL error codes

[dmagda]

Alex P, Vladimir,

Please confirm that the error codes documented for JDBC [1] driver are shared by all SQL APIs we have. If it’s so I would create Error Codes page under SQL Reference section and will provide error handling code snippets for JDBC, ODBC and the native APIs.

[1] https://apacheignite-sql.readme.io/v2.1/docs/error-codes

—
Denis

[Igor Sapego-2]

Error codes are different for ODBC and JDBC.

Best Regards,
Igor

On Thu, Oct 19, 2017 at 3:23 AM, Denis Magda <[hidden email]> wrote:

> Alex P, Vladimir,
>
> Please confirm that the error codes documented for JDBC [1] driver are
> shared by all SQL APIs we have. If it’s so I would create Error Codes page
> under SQL Reference section and will provide error handling code snippets
> for JDBC, ODBC and the native APIs.
>
> [1] https://apacheignite-sql.readme.io/v2.1/docs/error-codes
>
> —
> Denis

[dmagda]

Igor,

Do you have them documented somewhere? Couldn’t find in the existing docs.

Vladimir, Alex P.,

Do we reuse the error codes developed for JDBC on the native APIs side (Java, .NET, C++)? On the JDBC page we say that the codes are ANSI SQL compliant and my guess that they have to be the same across all SQL APIs.

—
Denis

> On Oct 19, 2017, at 3:16 AM, Igor Sapego <[hidden email]> wrote:
>
> Error codes are different for ODBC and JDBC.
>
> Best Regards,
> Igor
>
> On Thu, Oct 19, 2017 at 3:23 AM, Denis Magda <[hidden email]> wrote:
>
>> Alex P, Vladimir,
>>
>> Please confirm that the error codes documented for JDBC [1] driver are
>> shared by all SQL APIs we have. If it’s so I would create Error Codes page
>> under SQL Reference section and will provide error handling code snippets
>> for JDBC, ODBC and the native APIs.
>>
>> [1] https://apacheignite-sql.readme.io/v2.1/docs/error-codes
>>
>> —
>> Denis

[Vladimir Ozerov]

No, they are not re-used. SQLSTATE is JDBC/ODBC-specific thing (and both
driver types have different codes).

On Thu, Oct 19, 2017 at 7:39 PM, Denis Magda <[hidden email]> wrote:

> Igor,
>
> Do you have them documented somewhere? Couldn’t find in the existing docs.
>
> Vladimir, Alex P.,
>
> Do we reuse the error codes developed for JDBC on the native APIs side
> (Java, .NET, C++)? On the JDBC page we say that the codes are ANSI SQL
> compliant and my guess that they have to be the same across all SQL APIs.
>
> —
> Denis
>
> > On Oct 19, 2017, at 3:16 AM, Igor Sapego <[hidden email]> wrote:
> >
> > Error codes are different for ODBC and JDBC.
> >
> > Best Regards,
> > Igor
> >
> > On Thu, Oct 19, 2017 at 3:23 AM, Denis Magda <[hidden email]> wrote:
> >
> >> Alex P, Vladimir,
> >>
> >> Please confirm that the error codes documented for JDBC [1] driver are
> >> shared by all SQL APIs we have. If it’s so I would create Error Codes
> page
> >> under SQL Reference section and will provide error handling code
> snippets
> >> for JDBC, ODBC and the native APIs.
> >>
> >> [1] https://apacheignite-sql.readme.io/v2.1/docs/error-codes
> >>
> >> —
> >> Denis
>
>

[dsetrakyan]

On Thu, Oct 19, 2017 at 9:48 AM, Vladimir Ozerov <[hidden email]>
wrote:

> No, they are not re-used. SQLSTATE is JDBC/ODBC-specific thing (and both
> driver types have different codes).
>

Vladimir, are there any error codes that come from the Ignite engine that
are shared between JDBC and ODBC drivers? What if the SQL execution is
triggered from Ignite API directly, what error codes are used then?

[dsetrakyan]

On Thu, Oct 19, 2017 at 2:48 PM, Alexander Paschenko <
[hidden email]> wrote:

> Dmitriy,
>
> There are Ignite specific codes, they are returned when queries are run
> via Ignite API. There are no codes explicitly shared by JDBC and ODBC,
> although some of them happen to be the same.
>

Thanks, Alex. Now it sounds that we propagate these codes to JDBC and ODBC
drivers right? In that case, we should have Generic Error Codes pages in
documentation which lists all the common error codes, right?

[dmagda]

Yes, we should document as much as we can here. Created a ticket in advance so that this is solved before 2.3 release:
https://issues.apache.org/jira/browse/IGNITE-6687 <https://issues.apache.org/jira/browse/IGNITE-6687>

—
Denis

> On Oct 19, 2017, at 3:51 PM, Alexander Paschenko <[hidden email]> wrote:
>
> I meant «that “commonization”», sorry.
>
> пт, 20 окт. 2017 г. в 1:49, Alexander Paschenko <[hidden email] <mailto:[hidden email]>>:
> I doubt that codes that are common between ODBC and JDBC really need that “communication”. Those are different sets of codes documented independently.
> On the other hand, Ignite specific codes thrown when queries are run via Ignite API are effectively of a third kind. Vladimir, what do you think, should we document those?
>
> - Alex
>
> пт, 20 окт. 2017 г. в 1:03, Dmitriy Setrakyan <[hidden email] <mailto:[hidden email]>>:
> On Thu, Oct 19, 2017 at 2:48 PM, Alexander Paschenko <[hidden email] <mailto:[hidden email]>> wrote:
> Dmitriy,
>
> There are Ignite specific codes, they are returned when queries are run via Ignite API. There are no codes explicitly shared by JDBC and ODBC, although some of them happen to be the same.
>
> Thanks, Alex. Now it sounds that we propagate these codes to JDBC and ODBC drivers right? In that case, we should have Generic Error Codes pages in documentation which lists all the common error codes, right?
>