November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3629) Teiid DDL columns options for Salesforce column have wrong name for "Calculated" property

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3629?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3629: ---------------------------------- > Teiid DDL columns options for Salesforce column have wrong name for "Calculated" property > ----------------------------------------------------------------------------------------- > > Key: TEIID-3629 > URL: https://issues.jboss.org/browse/TEIID-3629 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.8 > Reporter: Andrej Šmigala > Priority: Minor > Fix For: 8.12 > > Attachments: sfDDL.ddl > > > Back in 2014, Teiid & Teiid Designer synched our Salesforce constants/extension properties to facilitate DDL import. However, it appears that the teiid_sf:calculated constant wasn't converted properly to *teiid_sf:Calculated*. https://github.com/teiid/teiid/commit/88781c220e1afc79c889cfc5d7c1c3e5d8e... > I'm able to import the attached DDL if I change *teiid_sf:calculated* to *teiid_sf:Calculated*. > The following is logged in the error log multiple times when importing Salesforce from Teiid Connection. The imported model appears to work ok (tried previewing a couple tables). > {quote} > java.lang.Exception: The property definition "salesforce:calculated" could not be found. > at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.setPropertyValue(EmfModelObjectExtensionAssistant.java:485) > at org.teiid.designer.ddl.importer.node.EmfModelGenerator.setPropertyValue(EmfModelGenerator.java:1203) > at org.teiid.designer.ddl.importer.node.EmfModelGenerator.processExtensionProperties(EmfModelGenerator.java:1110) > at org.teiid.designer.ddl.importer.node.EmfModelGenerator.execute(EmfModelGenerator.java:219) > at org.teiid.designer.ddl.importer.DdlImporter.save(DdlImporter.java:324) > at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager$2.run(TeiidImportManager.java:802) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527) > at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:795) > at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197) > at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1182) > at org.jboss.reddeer.swt.handler.WidgetHandler$4.run(WidgetHandler.java:333) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:184) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:1) > at org.jboss.reddeer.swt.util.Display$ErrorHandlingRunnable.run(Display.java:150) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1182) > at org.jboss.reddeer.swt.handler.MenuHandler$5.run(MenuHandler.java:116) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:184) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:1) > at org.jboss.reddeer.swt.util.Display$ErrorHandlingRunnable.run(Display.java:150) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3586: ---------------------------------- > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3586: --------------------------------- Fix Version/s: 8.7.2.6_2 (was: 8.7.1.6_2) > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.2, 8.7.2.6_2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3592: --------------------------------- Fix Version/s: 8.7.2.6_2 (was: 8.7.1.6_2) > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2, 8.7.2.6_2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2936) Combining multiple 'in' criteria can prevent pushing criteria to database

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2936?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2936: --------------------------------- Fix Version/s: 8.7.2.6_2 (was: 8.7.1.6_2) > Combining multiple 'in' criteria can prevent pushing criteria to database > ------------------------------------------------------------------------- > > Key: TEIID-2936 > URL: https://issues.jboss.org/browse/TEIID-2936 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.7 > Reporter: Mike Higgins > Assignee: Steven Hawkins > Fix For: 8.8, 8.7.2.6_2 > > > When two 'in' criteria containing constant values on the same field are combined with an 'or', Teiid will combine the two into a single 'in' operation. > Since Oracle (for example) has a 1000 item limit on the 'in' values, if the resulting combined list contains more than 1000 values, it can no longer be pushed down into Oracle for execution. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3586: --------------------------------- Fix Version/s: 8.7.1.6_2 > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3586. -------------------------------- Resolution: Done > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.11.2, 8.12, 8.7.1.6_2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3592: ---------------------------------- > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3592: --------------------------------- Fix Version/s: 8.7.1.6_2 > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.12, 8.11.2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3586: ---------------------------------- > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2015