Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 361F0200D23 for ; Thu, 19 Oct 2017 23:11:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 34A2A1609EE; Thu, 19 Oct 2017 21:11:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A0ED01609D7 for ; Thu, 19 Oct 2017 23:11:22 +0200 (CEST) Received: (qmail 84331 invoked by uid 500); 19 Oct 2017 21:11:21 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 84320 invoked by uid 99); 19 Oct 2017 21:11:21 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Oct 2017 21:11:21 +0000 Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com [209.85.216.179]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1BEAD1A012F for ; Thu, 19 Oct 2017 21:11:20 +0000 (UTC) Received: by mail-qt0-f179.google.com with SMTP id f8so16193128qta.5 for ; Thu, 19 Oct 2017 14:11:19 -0700 (PDT) X-Gm-Message-State: AMCzsaUk5GMFOsVg/dL1hqASM2dg7mqgImg6Y4gTEIovWN3LK//+tLst b75leyKw+Z5shYpyVFvs+9EaB5TOETYF2jnRu/TXjQ== X-Google-Smtp-Source: ABhQp+T5WByzWlW4cFLqhI8N39V3jb3sL1wOzbJIhFQcC+KF9mz/4FVfhhWMBXHMVSfWRE0WKUF+oVOOpwkNuLr9cbA= X-Received: by 10.200.22.234 with SMTP id y39mr4021075qtk.59.1508447479272; Thu, 19 Oct 2017 14:11:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.28.3 with HTTP; Thu, 19 Oct 2017 14:10:38 -0700 (PDT) In-Reply-To: References: <73732EB5-2A9F-4874-B6C2-A20A9DD97AC0@apache.org> From: Dmitriy Setrakyan Date: Thu, 19 Oct 2017 14:10:38 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: SQL error codes To: dev@ignite.apache.org Cc: Denis Magda , Alexander Paschenko Content-Type: multipart/alternative; boundary="94eb2c043b6c2a29fa055beccccd" archived-at: Thu, 19 Oct 2017 21:11:23 -0000 --94eb2c043b6c2a29fa055beccccd Content-Type: text/plain; charset="UTF-8" On Thu, Oct 19, 2017 at 9:48 AM, Vladimir Ozerov 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? --94eb2c043b6c2a29fa055beccccd--