]
Van Halbert commented on TEIID-4412:
------------------------------------
I think this can be closed, as the new logic will now throw an exception when the primary
key is trying to be changed. It indicates that the object must be deleted and then
readded.
Incorrectly handling when trying to update attribute that is the
primar key
---------------------------------------------------------------------------
Key: TEIID-4412
URL:
https://issues.jboss.org/browse/TEIID-4412
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 9.1
Reporter: Van Halbert
Assignee: Van Halbert
Priority: Critical
The current logic doesn't handle when the attribute being updated is also the primary
key. The metadata from a dynamic vdb indicates this attribute to be updatable.
(1) I'm thinking the problem is that the attribute that is the primary key should not
be updatable, but in order to be changed, the object should be deleted and re-added.
(2) Or, would the preferred way to handle this is to allow it to be updatable, but change
the logic to check when this attribute is changing and internally perform a delete and
re-add.
I like option (1) because the user is in control, where (2) is done under the covers.