[
https://issues.apache.org/jira/browse/IGNITE-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815220#comment-16815220
]
Andrew Mashenkov commented on IGNITE-11563:
-------------------------------------------
[~pkouznet],
# Rounding\cast value to column scale-precision by default with an option to
disable this behavior looks acceptable. Let's make this like MsSql goes.
# It seems we can do nothing for cache API for now, but just point to decimal
limitations in Ignite documentation .
We could compare 2 decimals with rounding up to some common scale, but it is
impossible due to key are compares as byte[]. Even if we found a solution to
compare decimal fields without deserialization, comparing key binary objects
field-by-field will hit performance too much.
> 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 = ?}}
> 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-condition it
> works as expected:
> {{DELETE}} {{FROM}} {{AnyTable WHERE}} {{id = id AND}} {{id = ?}}
> I tested with a very simple table that was created with:
> {{CREATE TABLE testtable (}}
> {{ "ID" NUMBER(19,0),}}
> {{ "VALUE" VARCHAR2(255 CHAR),}}
> {{ PRIMARY KEY (ID)}}
> {{) WITH "template=replicated,cache_name=testtable"}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
