[JBoss JIRA] (TEIID-3818) Microsoft's Power BI desktop using ODBC uses unsupported name type
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3818?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3818:
---------------------------------------
This is effectively a metadata query for foreign key information. Looking at the 9.0 driver code this query should be getting the exported keys. We do have handling in our layer, but it looks to only account for imported keys. We'll resolve this with handling specific to the metadata query, rather than adding more general pg support.
> Microsoft's Power BI desktop using ODBC uses unsupported name type
> ------------------------------------------------------------------
>
> Key: TEIID-3818
> URL: https://issues.jboss.org/browse/TEIID-3818
> Project: Teiid
> Issue Type: Feature Request
> Components: ODBC
> Affects Versions: 8.11.5
> Environment: Most likely not OS / hardware dependent.
> Reporter: Dave Nicodemus
> Assignee: Steven Hawkins
>
> Full history in this thread https://developer.jboss.org/message/945727#945727
> While attempting to use Client Microsoft's Power BI desktop using ODBC connecting to Teiid Embedded server using VDB with metadata tags.
> Received the following errors :
> {code}
> [36.864]ERROR from backend during send_query: 'SERROR'
> [36.865]ERROR from backend during send_query: 'C50000'
> [36.869]ERROR from backend during send_query: 'MTEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33.
> Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'
> [36.875]ERROR from backend during send_query: 'Dorg.teiid.jdbc.TeiidSQLException: TEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33.
> Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'
> [37.397]STATEMENT ERROR: func=PGAPI_ForeignKeys, desc='', errnum=1, errmsg='PGAPI_ForeignKeys query error'
> {code}
> Due to this query being generated by the BI tool :
> {code}
> 'select 'ScottTestMart'::name as PKTABLE_CAT,
> n2.nspname as PKTABLE_SCHEM,
> c2.relname as PKTABLE_NAME,
> a2.attname as PKCOLUMN_NAME,
> 'ScottTestMart'::name as FKTABLE_CAT,
> n1.nspname as FKTABLE_SCHEM,
> c1.relname as FKTABLE_NAME,
> a1.attname as FKCOLUMN_NAME,
> i::int2 as KEY_SEQ,
> case ref.confupdtype
> when 'c' then 0::int2
> when 'n' then 2::int2
> when 'd' then 4::int2
> when 'r' then 1::int2
> else 3::int2
> end as UPDATE_RULE,
> case ref.confdeltype
> when 'c' then 0::int2
> when 'n' then 2::int2
> when 'd' then 4::int2
> when 'r' then 1::int2
> else 3::int2
> end as DELETE_RULE,
> ref.conname as FK_NAME,
> cn.conname as PK_NAME,
> case
> when ref.condeferrable then
> case
> when ref.condeferred then 5::int2
> else 6::int2
> end
> else 7::int2
> end as DEFERRABLITY
> from
> ((((((( (select cn.oid, conrelid, conkey, confrelid, confkey,
> generate_series(array_lower(conkey, 1), array_upper(conkey, 1)) as i,
> confupdtype, confdeltype, conname,
> condeferrable, condeferred
> from pg_catalog.pg_constraint cn,
> pg_catalog.pg_class c,
> pg_catalog.pg_namespace n
> where contype = 'f'
> and confrelid = c.oid
> and relname = 'Categories'
> and n.oid = c.relnamespace
> and n.nspname = 'ScottTestMart'
> ) ref
> inner join pg_catalog.pg_class c1
> on c1.oid = ref.conrelid)
> inner join pg_catalog.pg_namespace n1
> on n1.oid = c1.relnamespace)
> inner join pg_catalog.pg_attribute a1
> on a1.attrelid = c1.oid
> and a1.attnum = conkey[i])
> inner join pg_catalog.pg_class c2
> on c2.oid = ref.confrelid)
> inner join pg_catalog.pg_namespace n2
> on n2.oid = c2.relnamespace)
> inner join pg_catalog.pg_attribute a2
> on a2.attrelid = c2.oid
> and a2.attnum = confkey[i])
> left outer join pg_catalog.pg_constraint cn
> on cn.conrelid = ref.confrelid
> and cn.contype = 'p')
> order by ref.oid, ref.i'
> {code}
> Apparently due to:
> {quote}
> Our pg layer isn't currently handling the name type. It's not a full pg emulation, rather it's targeted at supporting as much of Teiid SQL as possible. So this would need to be captured as an issue.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3818) Microsoft's Power BI desktop using ODBC uses unsupported name type
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3818?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3818:
---------------------------------------
Is this the postgresql odbc driver, and what version?
> Microsoft's Power BI desktop using ODBC uses unsupported name type
> ------------------------------------------------------------------
>
> Key: TEIID-3818
> URL: https://issues.jboss.org/browse/TEIID-3818
> Project: Teiid
> Issue Type: Feature Request
> Components: ODBC
> Affects Versions: 8.11.5
> Environment: Most likely not OS / hardware dependent.
> Reporter: Dave Nicodemus
> Assignee: Steven Hawkins
>
> Full history in this thread https://developer.jboss.org/message/945727#945727
> While attempting to use Client Microsoft's Power BI desktop using ODBC connecting to Teiid Embedded server using VDB with metadata tags.
> Received the following errors :
> {code}
> [36.864]ERROR from backend during send_query: 'SERROR'
> [36.865]ERROR from backend during send_query: 'C50000'
> [36.869]ERROR from backend during send_query: 'MTEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33.
> Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'
> [36.875]ERROR from backend during send_query: 'Dorg.teiid.jdbc.TeiidSQLException: TEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33.
> Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'
> [37.397]STATEMENT ERROR: func=PGAPI_ForeignKeys, desc='', errnum=1, errmsg='PGAPI_ForeignKeys query error'
> {code}
> Due to this query being generated by the BI tool :
> {code}
> 'select 'ScottTestMart'::name as PKTABLE_CAT,
> n2.nspname as PKTABLE_SCHEM,
> c2.relname as PKTABLE_NAME,
> a2.attname as PKCOLUMN_NAME,
> 'ScottTestMart'::name as FKTABLE_CAT,
> n1.nspname as FKTABLE_SCHEM,
> c1.relname as FKTABLE_NAME,
> a1.attname as FKCOLUMN_NAME,
> i::int2 as KEY_SEQ,
> case ref.confupdtype
> when 'c' then 0::int2
> when 'n' then 2::int2
> when 'd' then 4::int2
> when 'r' then 1::int2
> else 3::int2
> end as UPDATE_RULE,
> case ref.confdeltype
> when 'c' then 0::int2
> when 'n' then 2::int2
> when 'd' then 4::int2
> when 'r' then 1::int2
> else 3::int2
> end as DELETE_RULE,
> ref.conname as FK_NAME,
> cn.conname as PK_NAME,
> case
> when ref.condeferrable then
> case
> when ref.condeferred then 5::int2
> else 6::int2
> end
> else 7::int2
> end as DEFERRABLITY
> from
> ((((((( (select cn.oid, conrelid, conkey, confrelid, confkey,
> generate_series(array_lower(conkey, 1), array_upper(conkey, 1)) as i,
> confupdtype, confdeltype, conname,
> condeferrable, condeferred
> from pg_catalog.pg_constraint cn,
> pg_catalog.pg_class c,
> pg_catalog.pg_namespace n
> where contype = 'f'
> and confrelid = c.oid
> and relname = 'Categories'
> and n.oid = c.relnamespace
> and n.nspname = 'ScottTestMart'
> ) ref
> inner join pg_catalog.pg_class c1
> on c1.oid = ref.conrelid)
> inner join pg_catalog.pg_namespace n1
> on n1.oid = c1.relnamespace)
> inner join pg_catalog.pg_attribute a1
> on a1.attrelid = c1.oid
> and a1.attnum = conkey[i])
> inner join pg_catalog.pg_class c2
> on c2.oid = ref.confrelid)
> inner join pg_catalog.pg_namespace n2
> on n2.oid = c2.relnamespace)
> inner join pg_catalog.pg_attribute a2
> on a2.attrelid = c2.oid
> and a2.attnum = confkey[i])
> left outer join pg_catalog.pg_constraint cn
> on cn.conrelid = ref.confrelid
> and cn.contype = 'p')
> order by ref.oid, ref.i'
> {code}
> Apparently due to:
> {quote}
> Our pg layer isn't currently handling the name type. It's not a full pg emulation, rather it's targeted at supporting as much of Teiid SQL as possible. So this would need to be captured as an issue.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3821) Expand xml output types
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3821?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3821.
-----------------------------------
Fix Version/s: 8.12.2
8.13
Resolution: Done
Added blob/varbinary output for xml, and expanded the validation of xml and text content types appropriately. Did not add handling for array output yet as more research is needed as to what the correct approach is.
If hex output is needed, we may need to add an option clause similar to https://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.5.0/com.ibm.db2.l...
Also was made for xmltable, but it may make sense to accept base64 binary by default instead to match the default output behavior.
> Expand xml output types
> -----------------------
>
> Key: TEIID-3821
> URL: https://issues.jboss.org/browse/TEIID-3821
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12.2, 8.13
>
>
> XMLELEMENT/XMLFOREST, etc. should support outputting binary/blob as base64 binary. Also array values could be output as a sequence - although support seems to be inconsistent there with other vendors.
> Ideally XMLTABLE should support base64 binary in addition to hex binary as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3821) Expand xml output types
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3821:
-------------------------------------
Summary: Expand xml output types
Key: TEIID-3821
URL: https://issues.jboss.org/browse/TEIID-3821
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
XMLELEMENT/XMLFOREST, etc. should support outputting binary/blob as base64 binary. Also array values could be output as a sequence - although support seems to be inconsistent there with other vendors.
Ideally XMLTABLE should support base64 binary in addition to hex binary as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3819) SimpleDB NullPointerException when inserting null value
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3819?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3819.
-----------------------------------
Fix Version/s: 8.12.2
8.13
Resolution: Done
> SimpleDB NullPointerException when inserting null value
> -------------------------------------------------------
>
> Key: TEIID-3819
> URL: https://issues.jboss.org/browse/TEIID-3819
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 8.12.2, 8.13
>
> Attachments: simpledb-vdb.xml, simpledb.cli
>
>
> When performing INSERT query, where one of the values is null, NullPointerException is thrown.
> Example query:
> {code:sql}
> INSERT INTO SMallA(ItemName,doublenum) VALUES ('nullRow',null)
> {code}
> Stack trace in teiid's console:
> {code:plain}
> 13:59:57,789 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue35) TEIID30019 Unexpected exception for request dypFs9C3QJ3B.14: java.lang.NullPointerException
> at org.teiid.resource.adapter.simpledb.SimpleDBConnectionImpl.addAttribute(SimpleDBConnectionImpl.java:255)
> at org.teiid.resource.adapter.simpledb.SimpleDBConnectionImpl.performInsert(SimpleDBConnectionImpl.java:223)
> at org.teiid.translator.simpledb.SimpleDBInsertExecute.execute(SimpleDBInsertExecute.java:52)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:363) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:330) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3820) SimpleDB column import order may not be consistent
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3820?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3820.
-----------------------------------
Resolution: Done
Switched to use a linked hash map and added a test. Full consistency cannot be guaranteed as it's data dependent (as is the notion of an array column), but at least for the same source data we should see the same ordering reported.
> SimpleDB column import order may not be consistent
> --------------------------------------------------
>
> Key: TEIID-3820
> URL: https://issues.jboss.org/browse/TEIID-3820
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12.2, 8.13
>
>
> The attributes are first ordered in a HashMap, so the order from the source is not preserved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3820) SimpleDB column import order may not be consistent
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3820:
-------------------------------------
Summary: SimpleDB column import order may not be consistent
Key: TEIID-3820
URL: https://issues.jboss.org/browse/TEIID-3820
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12.2, 8.13
The attributes are first ordered in a HashMap, so the order from the source is not preserved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3819) SimpleDB NullPointerException when inserting null value
by Jan Stastny (JIRA)
Jan Stastny created TEIID-3819:
----------------------------------
Summary: SimpleDB NullPointerException when inserting null value
Key: TEIID-3819
URL: https://issues.jboss.org/browse/TEIID-3819
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.7.1.6_2
Reporter: Jan Stastny
Assignee: Steven Hawkins
Attachments: simpledb-vdb.xml, simpledb.cli
When performing INSERT query, where one of the values is null, NullPointerException is thrown.
Example query:
{code:sql}
INSERT INTO SMallA(ItemName,doublenum) VALUES ('nullRow',null)
{code}
Stack trace in teiid's console:
{code:plain}
13:59:57,789 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue35) TEIID30019 Unexpected exception for request dypFs9C3QJ3B.14: java.lang.NullPointerException
at org.teiid.resource.adapter.simpledb.SimpleDBConnectionImpl.addAttribute(SimpleDBConnectionImpl.java:255)
at org.teiid.resource.adapter.simpledb.SimpleDBConnectionImpl.performInsert(SimpleDBConnectionImpl.java:223)
at org.teiid.translator.simpledb.SimpleDBInsertExecute.execute(SimpleDBInsertExecute.java:52)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:363) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:330) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79]
at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3813) Informix translator - convert function in definition of view is not pushed down
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3813?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3813:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1279400|https://bugzilla.redhat.com/show_bug.cgi?id=1279400] from NEW to MODIFIED
> Informix translator - convert function in definition of view is not pushed down
> -------------------------------------------------------------------------------
>
> Key: TEIID-3813
> URL: https://issues.jboss.org/browse/TEIID-3813
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 8.12.2, 8.13
>
>
> I defined a view (see definition below). When I try to select all rows from the view, teiid/informix jdbc driver throws an exception.
> Teiid DDL:
> {code:sql}
> CREATE VIEW U6 (StringCol string,
> IntCol integer)
> AS
> SELECT CONVERT(BQT1.SmallA.IntNum, string) AS StringCol, BQT1.SmallA.IntNum AS IntCol
> FROM BQT1.SmallA
> UNION ALL
> SELECT BQT1.SmallB.StringNum, CONVERT(BQT1.SmallB.StringNum, integer)
> FROM BQT1.SmallB;
> }
> {code}
> Query:
> {code:sql}
> SELECT * FROM VQT.U6
> {code}
> Source-specific query
> {code:sql}
> SELECT g_1.intnum AS c_0, g_1.intnum AS c_1 FROM smalla AS g_1 UNION ALL SELECT g_0.stringnum AS c_0, g_0.stringnum AS c_1 FROM smallb AS g_0
> {code}
> Actual exception:
> {code:text}
> Caused by: java.sql.SQLException: The statement failed because corresponding column data types must be compatible for each UNION, INTERSECT, or MINUS query.
> at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:408)
> at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3178)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3818) Microsoft's Power BI desktop using ODBC uses unsupported name type
by Dave Nicodemus (JIRA)
Dave Nicodemus created TEIID-3818:
-------------------------------------
Summary: Microsoft's Power BI desktop using ODBC uses unsupported name type
Key: TEIID-3818
URL: https://issues.jboss.org/browse/TEIID-3818
Project: Teiid
Issue Type: Feature Request
Components: ODBC
Affects Versions: 8.11.5
Environment: Most likely not OS / hardware dependent.
Reporter: Dave Nicodemus
Assignee: Steven Hawkins
Full history in this thread https://developer.jboss.org/message/945727#945727
While attempting to use Client Microsoft's Power BI desktop using ODBC connecting to Teiid Embedded server using VDB with metadata tags.
Received the following errors :
{code}
[36.864]ERROR from backend during send_query: 'SERROR'
[36.865]ERROR from backend during send_query: 'C50000'
[36.869]ERROR from backend during send_query: 'MTEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33.
Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'
[36.875]ERROR from backend during send_query: 'Dorg.teiid.jdbc.TeiidSQLException: TEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33.
Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'
[37.397]STATEMENT ERROR: func=PGAPI_ForeignKeys, desc='', errnum=1, errmsg='PGAPI_ForeignKeys query error'
{code}
Due to this query being generated by the BI tool :
{code}
'select 'ScottTestMart'::name as PKTABLE_CAT,
n2.nspname as PKTABLE_SCHEM,
c2.relname as PKTABLE_NAME,
a2.attname as PKCOLUMN_NAME,
'ScottTestMart'::name as FKTABLE_CAT,
n1.nspname as FKTABLE_SCHEM,
c1.relname as FKTABLE_NAME,
a1.attname as FKCOLUMN_NAME,
i::int2 as KEY_SEQ,
case ref.confupdtype
when 'c' then 0::int2
when 'n' then 2::int2
when 'd' then 4::int2
when 'r' then 1::int2
else 3::int2
end as UPDATE_RULE,
case ref.confdeltype
when 'c' then 0::int2
when 'n' then 2::int2
when 'd' then 4::int2
when 'r' then 1::int2
else 3::int2
end as DELETE_RULE,
ref.conname as FK_NAME,
cn.conname as PK_NAME,
case
when ref.condeferrable then
case
when ref.condeferred then 5::int2
else 6::int2
end
else 7::int2
end as DEFERRABLITY
from
((((((( (select cn.oid, conrelid, conkey, confrelid, confkey,
generate_series(array_lower(conkey, 1), array_upper(conkey, 1)) as i,
confupdtype, confdeltype, conname,
condeferrable, condeferred
from pg_catalog.pg_constraint cn,
pg_catalog.pg_class c,
pg_catalog.pg_namespace n
where contype = 'f'
and confrelid = c.oid
and relname = 'Categories'
and n.oid = c.relnamespace
and n.nspname = 'ScottTestMart'
) ref
inner join pg_catalog.pg_class c1
on c1.oid = ref.conrelid)
inner join pg_catalog.pg_namespace n1
on n1.oid = c1.relnamespace)
inner join pg_catalog.pg_attribute a1
on a1.attrelid = c1.oid
and a1.attnum = conkey[i])
inner join pg_catalog.pg_class c2
on c2.oid = ref.confrelid)
inner join pg_catalog.pg_namespace n2
on n2.oid = c2.relnamespace)
inner join pg_catalog.pg_attribute a2
on a2.attrelid = c2.oid
and a2.attnum = confkey[i])
left outer join pg_catalog.pg_constraint cn
on cn.conrelid = ref.confrelid
and cn.contype = 'p')
order by ref.oid, ref.i'
{code}
Apparently due to:
{quote}
Our pg layer isn't currently handling the name type. It's not a full pg emulation, rather it's targeted at supporting as much of Teiid SQL as possible. So this would need to be captured as an issue.
{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month