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

DDL Importer - problem with re-import when setting descriptions

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 8.2
    • 8.1
    • Import/Export
    • None
    • Hide

      1. Launch DDL Importer and select a DDL file from your filesystem.
      2. Choose target model, etc. Also, check the checkbox 'Set description of Model Entities to corresponding DDL statement'
      3. Finish the wizard - model is created.
      4. Now repeat the same process, choosing the same options and same target model.
      5. When the import finishes, all of the Model Entity names get changed to the typeName of entity - For example 'Base Table' instead of the actual name.

      Show
      1. Launch DDL Importer and select a DDL file from your filesystem. 2. Choose target model, etc. Also, check the checkbox 'Set description of Model Entities to corresponding DDL statement' 3. Finish the wizard - model is created. 4. Now repeat the same process, choosing the same options and same target model. 5. When the import finishes, all of the Model Entity names get changed to the typeName of entity - For example 'Base Table' instead of the actual name.

    Description

      When using the DDL importer for an existing model (update), the model entity names are getting reset. This only seems to occur if 'set description of Model Entities to corresponding DDL statement' checkbox is checked. The Entity names get changed to the default name of the entity.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. TEIIDDES-1706 During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users TEIIDDES-1739 Refactor DdlImporter into dialect-specific processors.

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              mdrillin1@redhat.com Mark Drilling (Inactive)
              mdrillin1@redhat.com Mark Drilling (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: