[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4105:
---------------------------------------
It's not that strange. This occurs anytime you make the relationships explicit - such as having a car that has a relationship to person as the driver and as the owner - rather than something more generic like a 1-many with a relationship field.
> ODATA: Duplicate NavigationProperty name
> ----------------------------------------
>
> Key: TEIID-4105
> URL: https://issues.jboss.org/browse/TEIID-4105
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.3
> Reporter: Ivan Lucas Vargas
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 9.0, 8.12.5
>
>
> Entity 1: TransferRule
> Entity 2: FinancialAccount
> TransferRule
> - sourceAccount : FinancialAccount
> - destination : FinancialAccount
> - other attributes
> the mapping to this for odata resolves to
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" />
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule"
> ToRole="financialaccount" />
> The navigation property name is duplicated with in transfer rule entity.
> Hence some of the Odata client see it as ambiguous element
> Is there a way to customise the Name to
> Name="src_financialaccount" and
> Name="dest_financialaccount"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4008:
---------------------------------------
No, this is not a regression.
> Sending teiid varbinary value (x'') to Microsoft SQL Server errors
> ------------------------------------------------------------------
>
> Key: TEIID-4008
> URL: https://issues.jboss.org/browse/TEIID-4008
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.2.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2
>
>
> When sending a query to Microsoft SQL Server with a varbinary in criteria:
> select * from debBinary where ipv6= x'FFFF6BBE85D8'
> It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8':
> [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8'
> [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ]
Johnathon Lee commented on TEIID-4008:
--------------------------------------
[~jdurani], does this represent a regression? ie: from the title, it doesn't appear to target postgres.
> Sending teiid varbinary value (x'') to Microsoft SQL Server errors
> ------------------------------------------------------------------
>
> Key: TEIID-4008
> URL: https://issues.jboss.org/browse/TEIID-4008
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.2.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2
>
>
> When sending a query to Microsoft SQL Server with a varbinary in criteria:
> select * from debBinary where ipv6= x'FFFF6BBE85D8'
> It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8':
> [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8'
> [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4008:
---------------------------------------
This isn't directly related to this fix. Postgresql is complaining because the default type is string for a select literal (which is really odd behavior sometimes). In most any other position in the query, this would work as expected. I'll just address under this same issue.
> Sending teiid varbinary value (x'') to Microsoft SQL Server errors
> ------------------------------------------------------------------
>
> Key: TEIID-4008
> URL: https://issues.jboss.org/browse/TEIID-4008
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.2.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2
>
>
> When sending a query to Microsoft SQL Server with a varbinary in criteria:
> select * from debBinary where ipv6= x'FFFF6BBE85D8'
> It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8':
> [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8'
> [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4008:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1313407|https://bugzilla.redhat.com/show_bug.cgi?id=1313407] from ON_QA to ASSIGNED
> Sending teiid varbinary value (x'') to Microsoft SQL Server errors
> ------------------------------------------------------------------
>
> Key: TEIID-4008
> URL: https://issues.jboss.org/browse/TEIID-4008
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.2.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2
>
>
> When sending a query to Microsoft SQL Server with a varbinary in criteria:
> select * from debBinary where ipv6= x'FFFF6BBE85D8'
> It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8':
> [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8'
> [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ]
Juraj Duráni reopened TEIID-4008:
---------------------------------
Fix does not work for postgresql translator.
*Query:* SELECT x'FF' FROM source.malla
*Source-specific command:* {code:sql}SELECT E'\\xFF' FROM "smalla" AS g_0{code}
*Exception:*
{code:text}
14:32:03,369 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue21) TEIID30020 Processing exception for request 4Z+LBdlIhjK4.7 'TEIID10076 Invalid conversion from type class java.lang.String with value '\xFF' to type class org.teiid.core.types.BinaryType'. Originally TransformationException DataTypeManager.java:931.: org.teiid.core.types.TransformationException: TEIID10076 Invalid conversion from type class java.lang.String with value '\xFF' to type class org.teiid.core.types.BinaryType
at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:931) [teiid-common-core-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.correctTypes(ConnectorWorkItem.java:531) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:398) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:207) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0-internal]
at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0-internal]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0-internal]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-internal]
{code}
> Sending teiid varbinary value (x'') to Microsoft SQL Server errors
> ------------------------------------------------------------------
>
> Key: TEIID-4008
> URL: https://issues.jboss.org/browse/TEIID-4008
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.2.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2
>
>
> When sending a query to Microsoft SQL Server with a varbinary in criteria:
> select * from debBinary where ipv6= x'FFFF6BBE85D8'
> It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8':
> [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8'
> [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4105:
-------------------------------------
I agree that the name of the table used for the navigation name, but the having multiple relations between *same* two tables seems like strange requirement.
> ODATA: Duplicate NavigationProperty name
> ----------------------------------------
>
> Key: TEIID-4105
> URL: https://issues.jboss.org/browse/TEIID-4105
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.3
> Reporter: Ivan Lucas Vargas
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 9.0, 8.12.5
>
>
> Entity 1: TransferRule
> Entity 2: FinancialAccount
> TransferRule
> - sourceAccount : FinancialAccount
> - destination : FinancialAccount
> - other attributes
> the mapping to this for odata resolves to
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" />
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule"
> ToRole="financialaccount" />
> The navigation property name is duplicated with in transfer rule entity.
> Hence some of the Odata client see it as ambiguous element
> Is there a way to customise the Name to
> Name="src_financialaccount" and
> Name="dest_financialaccount"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-4105:
--------------------------------
Comment: was deleted
(was: [~ivan.lucas.vargas] Can I get the DDL for the tables you are using. The navigation name is represented by the foreign key name (index name), typically these are unique for given table.)
> ODATA: Duplicate NavigationProperty name
> ----------------------------------------
>
> Key: TEIID-4105
> URL: https://issues.jboss.org/browse/TEIID-4105
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.3
> Reporter: Ivan Lucas Vargas
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 9.0, 8.12.5
>
>
> Entity 1: TransferRule
> Entity 2: FinancialAccount
> TransferRule
> - sourceAccount : FinancialAccount
> - destination : FinancialAccount
> - other attributes
> the mapping to this for odata resolves to
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" />
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule"
> ToRole="financialaccount" />
> The navigation property name is duplicated with in transfer rule entity.
> Hence some of the Odata client see it as ambiguous element
> Is there a way to customise the Name to
> Name="src_financialaccount" and
> Name="dest_financialaccount"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4105:
-------------------------------------
[~ivan.lucas.vargas] Can I get the DDL for the tables you are using. The navigation name is represented by the foreign key name (index name), typically these are unique for given table.
> ODATA: Duplicate NavigationProperty name
> ----------------------------------------
>
> Key: TEIID-4105
> URL: https://issues.jboss.org/browse/TEIID-4105
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.3
> Reporter: Ivan Lucas Vargas
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 9.0, 8.12.5
>
>
> Entity 1: TransferRule
> Entity 2: FinancialAccount
> TransferRule
> - sourceAccount : FinancialAccount
> - destination : FinancialAccount
> - other attributes
> the mapping to this for odata resolves to
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" />
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule"
> ToRole="financialaccount" />
> The navigation property name is duplicated with in transfer rule entity.
> Hence some of the Odata client see it as ambiguous element
> Is there a way to customise the Name to
> Name="src_financialaccount" and
> Name="dest_financialaccount"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months