[JBoss JIRA] (TEIID-4525) postgresql translator - remove all nulls & non printable characters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4525?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4525:
----------------------------------
Fix Version/s: 10.0
10.0
(was: Open To Community)
(was: 9.2)
> postgresql translator - remove all nulls & non printable characters
> -------------------------------------------------------------------
>
> Key: TEIID-4525
> URL: https://issues.jboss.org/browse/TEIID-4525
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Reporter: Omar Khan
> Priority: Minor
> Fix For: Open To Community, 10.0
>
>
> Would like to see the postgresql translator enhanced to add a feature to minimum remove nulls from text strings as some other databases i.e. Teradata allow for them where Postgres does not. This feature would behave in a similar manner as TrimSpaces, but simply remove all \u0000 characters.
> Furthermore, if possible, would like the ability to remove non printable characters to as another option provide another additional stripping mechanism, allowing the postgresql database to serve as a data cleaner if need be.
> Please refer to https://developer.jboss.org/thread/272644 for details
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (TEIID-4452) Pushdown SQL/XML
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4452?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4452:
----------------------------------
Fix Version/s: 10.0
10.0
(was: 9.2)
> Pushdown SQL/XML
> ----------------
>
> Key: TEIID-4452
> URL: https://issues.jboss.org/browse/TEIID-4452
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Affects Versions: 9.x
> Reporter: Tom Arnold
> Fix For: 10.0
>
>
> It would be helpful to pushdown SQL/XML functions for JDBC databases that support them.
> Databases:
> - Oracle
> - Postgres
> Functions:
> - XMLELEMENT
> - XMLATTRIBUTES
> - XMLAGG
> - XMLCONCAT
> We have an application that uses these functions and we support Oracle, Postgres, and Teiid (to integrate external data sources). Here's an example query generated by this application:
> {code:xml}
> select
> "ITEMS"."ITEM_ID" "ITEM_ID",
> (
> select xmlelement (
> name "attributes",
> xmlagg(
> xmlelement(
> name "attribute",
> xmlattributes(
> "ITEM_ATTRIBUTES"."ATTR_NAME" as "name",
> "ITEM_ATTRIBUTES"."ATTR_VALUE" as "value"
> )
> )
> )
> )
> from "ITEM_ATTRIBUTES" "ITEM_ATTRIBUTES"
> where (
> "ITEMS"."ITEM_ID" = "ITEM_ATTRIBUTES"."ITEM_ID"
> )
> ) "ITEM_ATTRIBUTES"
> {code}
> {code}
> ITEM_ID ITEM_ATTRIBUTES
> 3 <attributes><attribute name="foo" value="bar"></attribute><attribute name="baz" value="blah"></attribute></attributes>
> 4 <attributes><attribute name="foo" value="123"></attribute><attribute name="baz" value="456"></attribute></attributes>
> {code}
> When we are using Teiid queries like this do not work well because they cannot be pushed down, so we get N-many queries (one per row) and the query ends up taking much longer than if performed directly against Oracle/Postgres.
> Since SQL/XML is standard and supported by both Oracle/Postgres it would be good if queries like this could be pushed in their entirety so that there would be no performance difference between going through Teiid and native.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years