[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2584: --------------------------------------- A simple update approach would look something like a nocache merge (rather than a select, which would presumably return the rows). Given the limitation of our merge (which doesn't process row differences), we could instead use a refresh procedure like the above that identifies the table and the condition that identifies the affected rows (which would enable the update to work against tables without primary keys as well) and use dynamic sql to process the delete/insert. I also think the transformations table still needs some work or to be removed. Our notion of an insert/update/delete transformation is non-standard - typically these would be present under a triggers table. Associating the metadata with extension property keys also makes it more difficult to use. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira