Translate Criteria isn't working in MetaMatrix update/delete procedures
Environment
- MetaMatrix Enterprise Server 5.5.4
Issue
- We are not properly translating criteria in update/delete procedures. Instead, we are passing a Virtual Element name all the way down to the source system, without translating it to the actual NameInSource. This results in a bogus statement sent to the source system, and produces an error.
Resolution
The default TRANSLATE CRITERIA feature will only work against a single table. Since the query is against a virtual table whose transformation contains joins, a union, etc., MetaMatrix cannot resolve how to map the columns.
Fortunately TRANSLATE CRITERIA has a couple of keywords that will allow you to be more specific. They are ON and WITH. [1] WITH allows you to specify a column by column mapping [2].
[1] ftp://partners.redhat.com/metamatrix/JBEDSP_mmx554_3263/docs/developers/QuerySupportHandbook.pdf (Section 4.3.3.2 TRANSLATE CRITERIA)
[2] The is a bug with using the ON and WITH keywords that has been resolved with the latest server and designer patches for MetaMatrix version 5.5.4
You can download the latest server patch from http://ftp.redhat.com/pub/redhat/metamatrix/server_patch554
You can download the latest Enterprise Designer patch from: http://ftp.redhat.com/pub/redhat/metamatrix/designer_patch554
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments