Re: [teiid-designer-dev] default update procedures in 7.3
As part of this work, I would also propose removing the check box that enables/disables
specific update procedures and instead rely upon the overall view control ("supports
updates") and the use default check box.
The rationale for this change is that our default capabilities will be greatly expanded,
any situation that is not handled could just be shown as a validation warning, and if they
want to disallow a certain update type it would be best done through roles.
With these changes (of just expecting a null procedure in the index) it is also possible
to allow the usage of the default procedure without wiping out what the user may have
entered as the procedure - just don't write it into the index.
----- "Steven Hawkins" <shawkins(a)redhat.com> wrote:
https://jira.jboss.org/browse/TEIID-1349 covers changes to our
handling of default update procedures. In short we will no longer use
a generated procedure, but instead will leave the procedure null.
There is a UpdateValidator class that will provide a set of
ValidatorFailures and ValidatorWarnings related to the use of default
update handling.
There will be a related change
https://jira.jboss.org/browse/TEIID-1351 to remove the need to use
translate criteria based update procedures at all.
Steve