From issues-return-95158-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Apr 12 11:46:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id A6E0D180621 for ; Fri, 12 Apr 2019 13:46:01 +0200 (CEST) Received: (qmail 43271 invoked by uid 500); 12 Apr 2019 11:46:01 -0000 Mailing-List: contact issues-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 issues@ignite.apache.org Received: (qmail 43222 invoked by uid 99); 12 Apr 2019 11:46:00 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2019 11:46:00 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7D4CEE28B8 for ; Fri, 12 Apr 2019 11:46:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2D1CF24595 for ; Fri, 12 Apr 2019 11:46:00 +0000 (UTC) Date: Fri, 12 Apr 2019 11:46:00 +0000 (UTC) From: "Pavel Kuznetsov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-11563) DELETE WHERE does not work in prepared statements MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-11563?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 816194#comment-16816194 ]=20 Pavel Kuznetsov commented on IGNITE-11563: ------------------------------------------ One more point to think:=20 guess we decided to store internally decimal values with any scale. We have= column with type {{decimal(19,5)}} , but in cache we store decimal with sc= ale =3D 7. We perform select returning this value - what should we do in th= is case: return value with greater scale (7) that specified in the type (5)= ? Or should we round it ( to scale =3D 5)? Jdbc spec says we should return = full *precision* value.=20 > DELETE WHERE does not work in prepared statements > ------------------------------------------------- > > Key: IGNITE-11563 > URL: https://issues.apache.org/jira/browse/IGNITE-11563 > Project: Ignite > Issue Type: Bug > Components: sql > Affects Versions: 2.7 > Reporter: Stefan > Assignee: Pavel Kuznetsov > Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > With SQL I cannot delete a row using a prepared statement. The following = statement is simply ignored: > {{DELETE}} {{FROM}} {{AnyTable WHERE}} {{id =3D ?}} > This happens with JDBC-Thin and with ODBC so I suspect that the cluster = gets the correct data but handles it wrong. By adding an always-true-condit= ion it works as expected: > {{DELETE}} {{FROM}} {{AnyTable WHERE}} {{id =3D id AND}} {{id =3D ?}} > I tested with a very simple table that was created with: > {{CREATE TABLE testtable (}} > {{=C2=A0=C2=A0=C2=A0 "ID" NUMBER(19,0),}} > {{=C2=A0=C2=A0=C2=A0 "VALUE" VARCHAR2(255 CHAR),}} > {{=C2=A0=C2=A0=C2=A0 PRIMARY KEY (ID)}} > {{) WITH "template=3Dreplicated,cache_name=3Dtesttable"}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)