]
Steven Hawkins resolved TEIID-4700.
-----------------------------------
Fix Version/s: 9.2
9.1.3
Resolution: Done
Yes the doc note is for the Teiid side.
The change should address null handling in more scenarios - but there are some
circumstances that we cannot do anything about, such as
delete ... where col = ''
That would affect rows with both empty strings and null values.
Google translator inconsistent behavior for DELETE and SELECT for
null values
-----------------------------------------------------------------------------
Key: TEIID-4700
URL:
https://issues.jboss.org/browse/TEIID-4700
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 9.2
Environment: 9.2.0.Alpha2
Reporter: Lucie Fabrikova
Assignee: Steven Hawkins
Fix For: 9.2, 9.1.3
In teiid I observed following inconsistent behavior:
Q1: select intnum, intkey from smalla where intnum > -10 AND intnum < 20
Q2: delete from smalla where intnum > -10 AND intnum < 20
Q1 returns rows without null values for intnum, but Q2 deletes also rows with null values
for intnum.
I observed that if I remove the lower boundary (ie. Q3: select intnum, intkey from
smalla where intnum < 20 and similarly for delete), both selected and deleted rows
contain null values, so the result is consistent.
The server.log is empty, so I didn't attach it...