[JBoss JIRA] Created: (TEIIDDES-727) Preview of data based on previously created Conn Profile appears to use loopback conectr
by Paul Nittel (JIRA)
Preview of data based on previously created Conn Profile appears to use loopback conectr
----------------------------------------------------------------------------------------
Key: TEIIDDES-727
URL: https://jira.jboss.org/browse/TEIIDDES-727
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1.1
Environment: JBDS 4.0 Beta 2 (build is H12)
Reporter: Paul Nittel
I had an already-set up server which had previously been used to do similar previews and queries. I have no idea if that has anything to do with this.
I found that under some unusual set of circumstances, previewing relational data (select table, click preview button) may return data from the loopback connector, instead of the connection to the actual data source.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-806) Provide UI changes required for changes to behavior of Update queries in Teiid
by Barry LaFond (JIRA)
Provide UI changes required for changes to behavior of Update queries in Teiid
------------------------------------------------------------------------------
Key: TEIIDDES-806
URL: https://issues.jboss.org/browse/TEIIDDES-806
Project: Teiid Designer
Issue Type: Feature Request
Components: Documentation, Editors, Transformations
Affects Versions: 7.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Blocker
Fix For: 7.3
Teiid 7.3 release included changes to how Teiid processes Update queries. Teiid Designer will need to change the Transformation Editor to accommodate these changes.
The "Select" SQL will now be "analyzed" and validated to determine what "Update" capabilities will be enabled. The generated "Default" queries should also be removed and NO SQL defined if "Use Default" is enabled for Insert/Update/Delete
This is a departure from our legacy user experience, so the UI will have to be tweaked to recognize and interpret the new validation logic and display to user whether Insert/Update/Delete will be possible base don the Select.
One thought was decorating the I/U/D tab text with ICONS's to indicate "Allowed" or "Disallowed"
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-178) Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/
by Warren Gibson (JIRA)
Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-178
URL: https://jira.jboss.org/jira/browse/TEIIDDES-178
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 6.0.0
Environment: Windows XP Client
Reporter: Warren Gibson
Priority: Minor
I had downloaded Eclipse 3.4.1 and installed it as a fresh install. I got teiid_designer_6.0.0.v20090430 from SVN. The designer zip file was on my desktop. I took the normal steps to install designer. When it installed I got the following. This seems to happen with every install on the Windows client. Not sure if it is a defect or is related to the designer zip being on my desktop.
Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/
java.net.URISyntaxException: Relative path in absolute URI: jar://file:C:%5CDocuments%20and%20Settings%5Cadmindv.SLNTQM13%5CDesktop%5Cteiid_designer_6.0.0.v20090430.zip!/
at java.net.URI.checkPath(Unknown Source)
at java.net.URI.<init>(Unknown Source)
at org.eclipse.equinox.internal.p2.core.helpers.URLUtil.toURI(URLUtil.java:65)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorSelector.<init>(MirrorSelector.java:106)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getMirror(SimpleArtifactRepository.java:490)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:447)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:515)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:162)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:146)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:94)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:504)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:64)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months