[
https://issues.apache.org/jira/browse/IGNITE-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Albrecht updated IGNITE-4531:
-----------------------------------
Summary: Update DML operation not working for @QuerySqlField with name
(was: Update DML operation not working for QuerySQLField with name)
> Update DML operation not working for @QuerySqlField with name
> -------------------------------------------------------------
>
> Key: IGNITE-4531
> URL: https://issues.apache.org/jira/browse/IGNITE-4531
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.8
> Reporter: David Albrecht
> Priority: Critical
>
> After putting a java class Operation with
> {code}
> @QuerySqlField(name = "operationNumber", index = true)
> private String mOperationNumber;
> @QuerySqlField(index = true)
> private String mUuid;
> {code}
> in the cache. Via debug console I can see the following fields:
> _val:
> Operation [... ,mUuid=FF42930B6D3242B5A0B9D631E017027E, mOperationNumber =
> 0010, ...]
> and a column named: OPERATIONNUMBER with value 0010.
> When I use
> {code}
> UPDATE Operation set operationNumber = ? WHERE mUuid = ?
> {code}
> with the arguments
> [SCHEDULED, FF42930B6D3242B5A0B9D631E017027E]
> I can see the following values:
> Operation [... ,mUuid=FF42930B6D3242B5A0B9D631E017027E, mOperationNumber =
> 0010, operationNumber=SCHEDULED, ...]
> and a column named: OPERATIONNUMBER with value 0010.
> The column 'OPERATIONNUMBER' and the field 'mOperationNumber' is not updated!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
