Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. TEIIDDES-996

Create Web Service fails if the model contains 2 schemas with the same tablenames underneath

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.5
    • 7.4
    • Import/Export
    • Workaround Exists
    • Hide

      Multiple workarounds:
      1. Generate the web service models individually instead of at the model level. This will allow you to make the output view and schemas unigue in the "create web service" wizard.
      2. In order to keep both schemas underneath the same model all the tablenames in the second schema would need to be changed. This isn't a viable solution though if the models contain numerous tables with the same name.

      Show
      Multiple workarounds: 1. Generate the web service models individually instead of at the model level. This will allow you to make the output view and schemas unigue in the "create web service" wizard. 2. In order to keep both schemas underneath the same model all the tablenames in the second schema would need to be changed. This isn't a viable solution though if the models contain numerous tables with the same name.

    Description

      In Teiid Designer, if you import a Source Model that contains 2 schemas, each schema contains tables with the same name. Right-click > Modeling > Create Web Service fails:
      "The name table_a_OutputView is the same (ignoring case) as 1 other object(s) under the same parent."

      The default names for the table Output Views should also contain the schema/folder names, i.e. schemaA_tableA_OutputView.

      Attachments

        Issue Links

          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) TEIIDDES-968 Catalog and Schema should use different icons so that they can be distinquished as to their type

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-engineering-tejones Edwin Jones
              rhn-support-dsteigner Deborah Steigner (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: