[JBoss JIRA] (TEIIDDES-2867) Importing from Sybase JDBC uses default double-quoted name in source values
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2867?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2867.
----------------------------------
> Importing from Sybase JDBC uses default double-quoted name in source values
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2867
> URL: https://issues.jboss.org/browse/TEIIDDES-2867
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0, 9.0.7
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Labels: release_notes, verified_jbdsis-9.0.1
> Fix For: 10.0.1
>
>
> The Sybase JDBC DB does fails to support Name In Source values with double-quoted segments.
> Current importer will define a table as "mySchema"."myCatalog".".myTable" and a column NIS as "column_1"
> The d-quotes need to get customized on import to remove the d-quotes
> See TEIIDDES-2458 for further discussions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2867) Importing from Sybase JDBC uses default double-quoted name in source values
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2867?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2867:
-----------------------------------
Labels: release_notes verified_jbdsis-9.0.1 (was: )
> Importing from Sybase JDBC uses default double-quoted name in source values
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2867
> URL: https://issues.jboss.org/browse/TEIIDDES-2867
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0, 9.0.7
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Labels: release_notes, verified_jbdsis-9.0.1
> Fix For: 10.0.1
>
>
> The Sybase JDBC DB does fails to support Name In Source values with double-quoted segments.
> Current importer will define a table as "mySchema"."myCatalog".".myTable" and a column NIS as "column_1"
> The d-quotes need to get customized on import to remove the d-quotes
> See TEIIDDES-2458 for further discussions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2720) Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2720:
-----------------------------------
Labels: release_notes verified_jbdsis-9.0.1 (was: )
> Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB
> --------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2720
> URL: https://issues.jboss.org/browse/TEIIDDES-2720
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.1
> Fix For: 10.0, 9.2.1
>
> Attachments: export-dynamic-vdb-status-dialog.png
>
>
> [~blafond]:
> {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote}
> Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures.
> Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2720) Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2720.
----------------------------------
> Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB
> --------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2720
> URL: https://issues.jboss.org/browse/TEIIDDES-2720
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.1
> Fix For: 10.0, 9.2.1
>
> Attachments: export-dynamic-vdb-status-dialog.png
>
>
> [~blafond]:
> {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote}
> Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures.
> Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2868) texttable parsing error
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2868?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2868:
----------------------------------------
Tom... I just tested (UBUNTU) the same scenario...
1) Are you on Windows?
2) Can you maybe delete the last few characters after paste, then re-type them? Wondering if it's a special windows char that's getting in the way.
> texttable parsing error
> -----------------------
>
> Key: TEIIDDES-2868
> URL: https://issues.jboss.org/browse/TEIIDDES-2868
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Environment: Teiid Designer 10.0.0.Final-v20160413-1817-B4094 org.teiid.designer.feature.feature.group JBoss by Red Hat
> Reporter: Tom Johnston
> Attachments: marketdata-price.txt, QuickStartSource.xmi, QuickStartViewModel.xmi, screenshot-1.png, screenshot-2.png
>
>
> I successfully created a physical table and view using texttable.
> I can query it.
> I then manually created another view to a different file and it kept failing with a very ambiguous error when I tried validating.
> ERROR: Error in parsing of sql - null
> I then created another view with a diff name of the 1st view using the same copy/pasted transformation.. it too resulting with the same error:
> The auto-generated view verbiage that was created and that I re-used was:
> SELECT
> A.OldWAC, A.NewWAC
> FROM
> (EXEC SourceModel.getTextFiles('wac.txt')) AS f, TEXTTABLE(f.file COLUMNS OldWAC string, NewWAC string DELIMITER '|') AS A
> You can also clone the automatically created object, copy the transformation, clear the transformation, paste back the transformation and it too fails with the same error.
> ALSO if I deploy the 1st physical and view models to a vdb I can execute the view transformation that fails in designer fine from squirrel getting data returned.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2868) texttable parsing error
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2868?page=com.atlassian.jira.plu... ]
Tom Johnston commented on TEIIDDES-2868:
----------------------------------------
Matus:
I did a clean install of JBDS and Teiid Designer:
!screenshot-1.png!
!screenshot-2.png!
Created a source model (jdbc import of files)
Both source models and view models created as a result of steps above.
I then went to the view model
created a new table and pasted the contents for the transformation.
Result was the same:
The query is not parsable.
Error in parsing of sql - null
> texttable parsing error
> -----------------------
>
> Key: TEIIDDES-2868
> URL: https://issues.jboss.org/browse/TEIIDDES-2868
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Environment: Teiid Designer 10.0.0.Final-v20160413-1817-B4094 org.teiid.designer.feature.feature.group JBoss by Red Hat
> Reporter: Tom Johnston
> Attachments: marketdata-price.txt, QuickStartSource.xmi, QuickStartViewModel.xmi, screenshot-1.png, screenshot-2.png
>
>
> I successfully created a physical table and view using texttable.
> I can query it.
> I then manually created another view to a different file and it kept failing with a very ambiguous error when I tried validating.
> ERROR: Error in parsing of sql - null
> I then created another view with a diff name of the 1st view using the same copy/pasted transformation.. it too resulting with the same error:
> The auto-generated view verbiage that was created and that I re-used was:
> SELECT
> A.OldWAC, A.NewWAC
> FROM
> (EXEC SourceModel.getTextFiles('wac.txt')) AS f, TEXTTABLE(f.file COLUMNS OldWAC string, NewWAC string DELIMITER '|') AS A
> You can also clone the automatically created object, copy the transformation, clear the transformation, paste back the transformation and it too fails with the same error.
> ALSO if I deploy the 1st physical and view models to a vdb I can execute the view transformation that fails in designer fine from squirrel getting data returned.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2868) texttable parsing error
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2868?page=com.atlassian.jira.plu... ]
Tom Johnston updated TEIIDDES-2868:
-----------------------------------
Attachment: screenshot-1.png
> texttable parsing error
> -----------------------
>
> Key: TEIIDDES-2868
> URL: https://issues.jboss.org/browse/TEIIDDES-2868
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Environment: Teiid Designer 10.0.0.Final-v20160413-1817-B4094 org.teiid.designer.feature.feature.group JBoss by Red Hat
> Reporter: Tom Johnston
> Attachments: marketdata-price.txt, QuickStartSource.xmi, QuickStartViewModel.xmi, screenshot-1.png, screenshot-2.png
>
>
> I successfully created a physical table and view using texttable.
> I can query it.
> I then manually created another view to a different file and it kept failing with a very ambiguous error when I tried validating.
> ERROR: Error in parsing of sql - null
> I then created another view with a diff name of the 1st view using the same copy/pasted transformation.. it too resulting with the same error:
> The auto-generated view verbiage that was created and that I re-used was:
> SELECT
> A.OldWAC, A.NewWAC
> FROM
> (EXEC SourceModel.getTextFiles('wac.txt')) AS f, TEXTTABLE(f.file COLUMNS OldWAC string, NewWAC string DELIMITER '|') AS A
> You can also clone the automatically created object, copy the transformation, clear the transformation, paste back the transformation and it too fails with the same error.
> ALSO if I deploy the 1st physical and view models to a vdb I can execute the view transformation that fails in designer fine from squirrel getting data returned.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2868) texttable parsing error
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2868?page=com.atlassian.jira.plu... ]
Tom Johnston updated TEIIDDES-2868:
-----------------------------------
Attachment: screenshot-2.png
> texttable parsing error
> -----------------------
>
> Key: TEIIDDES-2868
> URL: https://issues.jboss.org/browse/TEIIDDES-2868
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Environment: Teiid Designer 10.0.0.Final-v20160413-1817-B4094 org.teiid.designer.feature.feature.group JBoss by Red Hat
> Reporter: Tom Johnston
> Attachments: marketdata-price.txt, QuickStartSource.xmi, QuickStartViewModel.xmi, screenshot-1.png, screenshot-2.png
>
>
> I successfully created a physical table and view using texttable.
> I can query it.
> I then manually created another view to a different file and it kept failing with a very ambiguous error when I tried validating.
> ERROR: Error in parsing of sql - null
> I then created another view with a diff name of the 1st view using the same copy/pasted transformation.. it too resulting with the same error:
> The auto-generated view verbiage that was created and that I re-used was:
> SELECT
> A.OldWAC, A.NewWAC
> FROM
> (EXEC SourceModel.getTextFiles('wac.txt')) AS f, TEXTTABLE(f.file COLUMNS OldWAC string, NewWAC string DELIMITER '|') AS A
> You can also clone the automatically created object, copy the transformation, clear the transformation, paste back the transformation and it too fails with the same error.
> ALSO if I deploy the 1st physical and view models to a vdb I can execute the view transformation that fails in designer fine from squirrel getting data returned.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months