[JBoss JIRA] (TEIIDDES-1782) DDL import wizard - add better control over selection of imported objects
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1782?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1782.
------------------------------------
Resolution: Rejected
Designer exposes Importer properties (Table Pattern, etc...) for the user to provide filtering for the DDL.
Rejecting
> DDL import wizard - add better control over selection of imported objects
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-1782
> URL: https://issues.jboss.org/browse/TEIIDDES-1782
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Mark Drilling
> Fix For: 8.5
>
>
> User request to provide better control over which object types are imported via the DDL importer:
> It would be nice to be able to select which objects (like the jdbc importer of selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the jdbc importer wizard to provide the same options.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1811.
------------------------------------
Resolution: Cannot Reproduce Bug
Can't reproduce
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jane Li
> Priority: Minor
> Fix For: 8.5
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
> See: https://community.jboss.org/message/830569
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2148) missing rest properties (method etc)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2148?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2148:
----------------------------------------
I verified that the rest.mxd is in Alpha2.
Could you add details and screen pics of which properties you entered (panels/dialogs) and where you were expecting them to be shown afterwards?
> missing rest properties (method etc)
> ------------------------------------
>
> Key: TEIIDDES-2148
> URL: https://issues.jboss.org/browse/TEIIDDES-2148
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.5
> Environment: windows
> Reporter: luca gioppo
> Labels: rest
>
> After creating the procedure with the wizard there are no more the properties aviable in the usual place, have been asked to enter them but not shown afterwards.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2127) Problem with SF import using Teiid Connection importer - keys not resolved
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2127?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2127 at 5/6/14 11:27 PM:
-----------------------------------------------------------------
Looking at the end of each file I see 2 differences:
1) REFERENCES changed from ApexPage >> importVDBSrcModel.ApexPage (Id)
2) All the OPTIONS keys for SF changed from *"Supports XXXXXX"* to *supportsXXXXX*
- Note that these changes mostly likely broke Modeshape's Teiid DDL Parser logic as well as are incompatible with Designers SF built-in MED
=================
8.6 version
CONSTRAINT Id_PK PRIMARY KEY(Id),
CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES ApexPage
) OPTIONS (UPDATABLE TRUE, Custom 'false', "Supports Create" 'true', "Supports Delete" 'true', "Supports Merge" 'false', "Supports Query" 'true', "Supports Replicate" 'true', "Supports Retrieve" 'true', "Supports Search" 'false');
=================
8.7 version
CONSTRAINT Id_PK PRIMARY KEY(Id),
CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES importVDBSrcModel.ApexPage (Id)
) OPTIONS (UPDATABLE TRUE, custom 'false', supportsCreate 'true', supportsDelete 'true', supportsMerge 'false', supportsQuery 'true', supportsReplicate 'true', supportsRetrieve 'true', supportsSearch 'false');
=================
was (Author: blafond):
Looking at the end of each file I see 2 differences:
1) REFERENCES changed from ApexPage >> importVDBSrcModel.ApexPage (Id)
2) All the OPTIONS keys for SF changed from *"Supports XXXXXX"* to *supportsXXXXX*
- Note that these changes mostly likely broke Modeshape's Teiid DDL Parser logic as well as are incompatible with Designers SF built-in MED
=================
8.6 version
CONSTRAINT Id_PK PRIMARY KEY(Id),
CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES ApexPage
) OPTIONS (UPDATABLE TRUE, Custom 'false', "Supports Create" 'true', "Supports Delete" 'true', "Supports Merge" 'false', "Supports Query" 'true', "Supports Replicate" 'true', "Supports Retrieve" 'true', "Supports Search" 'false');
=================
8.7 version
CONSTRAINT Id_PK PRIMARY KEY(Id),
CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES importVDBSrcModel.ApexPage (Id)
) OPTIONS (UPDATABLE TRUE, custom 'false', supportsCreate 'true', supportsDelete 'true', supportsMerge 'false', supportsQuery 'true', supportsReplicate 'true', supportsRetrieve 'true', supportsSearch 'false');
=================
> Problem with SF import using Teiid Connection importer - keys not resolved
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2127
> URL: https://issues.jboss.org/browse/TEIIDDES-2127
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: exportedDDL-DV6.ddl, exportedDDL-Teiid87.ddl
>
>
> There is a problem with Salesforce import using the Teiid Connection importer in Designer 8.5 when connecting to a teiid 8.7 instance - the keys are not getting resolved, resulting in numerous model errors after import.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2127) Problem with SF import using Teiid Connection importer - keys not resolved
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2127?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2127:
----------------------------------------
Looking at the end of each file I see 2 differences:
1) REFERENCES changed from ApexPage >> importVDBSrcModel.ApexPage (Id)
2) All the OPTIONS keys for SF changed from *"Supports XXXXXX"* to *supportsXXXXX*
- Note that these changes mostly likely broke Modeshape's Teiid DDL Parser logic as well as are incompatible with Designers SF built-in MED
=================
8.6 version
CONSTRAINT Id_PK PRIMARY KEY(Id),
CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES ApexPage
) OPTIONS (UPDATABLE TRUE, Custom 'false', "Supports Create" 'true', "Supports Delete" 'true', "Supports Merge" 'false', "Supports Query" 'true', "Supports Replicate" 'true', "Supports Retrieve" 'true', "Supports Search" 'false');
=================
8.7 version
CONSTRAINT Id_PK PRIMARY KEY(Id),
CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES importVDBSrcModel.ApexPage (Id)
) OPTIONS (UPDATABLE TRUE, custom 'false', supportsCreate 'true', supportsDelete 'true', supportsMerge 'false', supportsQuery 'true', supportsReplicate 'true', supportsRetrieve 'true', supportsSearch 'false');
=================
> Problem with SF import using Teiid Connection importer - keys not resolved
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2127
> URL: https://issues.jboss.org/browse/TEIIDDES-2127
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: exportedDDL-DV6.ddl, exportedDDL-Teiid87.ddl
>
>
> There is a problem with Salesforce import using the Teiid Connection importer in Designer 8.5 when connecting to a teiid 8.7 instance - the keys are not getting resolved, resulting in numerous model errors after import.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2127) Problem with SF import using Teiid Connection importer - keys not resolved
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2127?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2127:
------------------------------------
Attachment: exportedDDL-DV6.ddl
exportedDDL-Teiid87.ddl
The Foreign Key DDL has changed... Attached DV6 version is imported OK, Teiid87 version is not.
> Problem with SF import using Teiid Connection importer - keys not resolved
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2127
> URL: https://issues.jboss.org/browse/TEIIDDES-2127
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: exportedDDL-DV6.ddl, exportedDDL-Teiid87.ddl
>
>
> There is a problem with Salesforce import using the Teiid Connection importer in Designer 8.5 when connecting to a teiid 8.7 instance - the keys are not getting resolved, resulting in numerous model errors after import.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2142) 'New VDB Data Role' Dialog needs layout improvement
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2142?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2142.
------------------------------------
Resolution: Done
Done
> 'New VDB Data Role' Dialog needs layout improvement
> ---------------------------------------------------
>
> Key: TEIIDDES-2142
> URL: https://issues.jboss.org/browse/TEIIDDES-2142
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Dialogs
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.5
>
> Attachments: data-role-dialog.png
>
>
> In VDB Editor, choose the data roles tab - then click to add a new data role.
> The resulting 'New VDB Data Role' dialog needs rework of the layout. Currently the center panel buttons are mostly hidden, and expanding the dialog size is still not sufficient.
> Recommend making this a tabbed panel - there's too much content on the current page.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2142) 'New VDB Data Role' Dialog needs layout improvement
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2142?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2142:
-----------------------------------
Attachment: data-role-dialog.png
> 'New VDB Data Role' Dialog needs layout improvement
> ---------------------------------------------------
>
> Key: TEIIDDES-2142
> URL: https://issues.jboss.org/browse/TEIIDDES-2142
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Dialogs
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.5
>
> Attachments: data-role-dialog.png
>
>
> In VDB Editor, choose the data roles tab - then click to add a new data role.
> The resulting 'New VDB Data Role' dialog needs rework of the layout. Currently the center panel buttons are mostly hidden, and expanding the dialog size is still not sufficient.
> Recommend making this a tabbed panel - there's too much content on the current page.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months