[JBoss JIRA] (TEIIDDES-1994) Quick Fix for names requiring double-quote problem marker
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1994?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-1994.
----------------------------------
Resolution: Out of Date
We've added reserved word checks in the importers to wrap them in double-quotes. This includes working with vdb.xml/DDL
> Quick Fix for names requiring double-quote problem marker
> ---------------------------------------------------------
>
> Key: TEIIDDES-1994
> URL: https://issues.jboss.org/browse/TEIIDDES-1994
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Validation
> Affects Versions: 8.3.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: Future
>
>
> TEIIDDES-1993 introducted a new validation rule that checks to see if object names require double-quoting to be valid as Teiid runtime metadata.
> Designer's JDBC Importer allows using fully qualified names for table names (schema.table).
> Example: PARTSSUPPLIER.SUPPLIER will fail.
> Add a Quick Fix to turn hjelp turn this problem marker type into a simple fix of the name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-2003) Usability - In a model, group by types (i.e, Table, procedure, etc.)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2003?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2003.
----------------------------------
Resolution: Won't Do
> Usability - In a model, group by types (i.e, Table, procedure, etc.)
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2003
> URL: https://issues.jboss.org/browse/TEIIDDES-2003
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: Komodo
>
>
> From a usability standpoint, and when working with large models, it would good to group by type (i.e, Table, procedure, etc.) when laying out a model in the tree on the left.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-1985) Better formating of SQL in transformation editor
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1985?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-1985.
----------------------------------
Resolution: Out of Date
> Better formating of SQL in transformation editor
> ------------------------------------------------
>
> Key: TEIIDDES-1985
> URL: https://issues.jboss.org/browse/TEIIDDES-1985
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration, Editors, Usability
> Affects Versions: 8.2, 8.3
> Environment: Windows 7 sp1 64 bit, Eclipse Kepler build: 20130614-0229, JDK 1.6.0_45
> Reporter: Patrick Deenen
> Priority: Minor
>
> Feature Improvement Request: Beautify SQL format in SQL transformation box. Currently all new lines are removed from the text behind SQL reserved words like SELECT, JOIN, FROM and WHERE. This doesn't improve readability, hence give the user the choice to have the SQL auto formatted or to maintain the original text or improve the auto format.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-1846) Top Down modeling, when importing to create views, allow for default syntax to applied
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1846?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-1846.
----------------------------------
Resolution: Won't Do
> Top Down modeling, when importing to create views, allow for default syntax to applied
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1846
> URL: https://issues.jboss.org/browse/TEIIDDES-1846
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: Future
>
>
> When a user is starting from a top-down approach (building the views) to design their data layers, and will be performing an import to create the view layer, it would speed up the iterative development of build / deploy / test (not preview) if when the view is built (on import), it can contain valid syntax so that the model will validate. Example of syntax could be, "Select '1'" or "Select 'view not defined'" or throw an exception. This would enable the modeler to implement the views at their pace and have it deployable, rather than having to go thru every view and add syntax before its valid. This is akin to JAVA and NOOP'ing the methods.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-1553) Executing SQL in the SQL Scrapbook fails if SQL not on one line.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1553?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-1553.
----------------------------------
Resolution: Won't Fix
This is a Data Tools issue and with the new Preview VDB.xml dialog users can define their own sql for a given view.
> Executing SQL in the SQL Scrapbook fails if SQL not on one line.
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1553
> URL: https://issues.jboss.org/browse/TEIIDDES-1553
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Reporter: Samuel Mendenhall
>
> After adding an existing Teiid instance to the Datasource Explorer and opening the SQL Scrapbook to execute SQL against that Teiid connection, the SQL must be executed on one line otherwise an error is thrown:
> Remote org.teiid.api.exception.query.QueryParserException: Parsing error: Encountered "-" at line 1, column 1.
> Was expecting one of:
> "alter" ...
> "call" ...
> "create" ...
> "delete" ...
> "drop" ...
> "exec" ...
> "execute" ...
> "insert" ...
> "select" ...
> "table" ...
> ...
> This happens specifically when running "Execute Current Text" / option+s
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-1656) Migrate and publish legacy E2E test scripts to community as how-to use-cases
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1656?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-1656.
----------------------------------
Resolution: Won't Do
> Migrate and publish legacy E2E test scripts to community as how-to use-cases
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-1656
> URL: https://issues.jboss.org/browse/TEIIDDES-1656
> Project: Teiid Designer
> Issue Type: Task
> Components: Documentation
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: Future
>
>
> The legacy (MetaMatrix) E2E test scripts have been migrated in part to work with Teiid & Teiid Designer. With the change to Teiid 8.x server and new Teiid Designer features, it makes sense to fix and publish the appropriate test scripts as "How To" documents (WIKI).
> This would include publishing the metadata used for these use-cases which use public Books, Employees, Products, Customers, Accounts, PartsSupplier data.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-1508) Add ability to Build a EDS VDB via APIe
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1508?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-1508.
----------------------------------
Resolution: Won't Do
DSB and follow-on Web UI development using komodo engine is implementing this scenario
> Add ability to Build a EDS VDB via APIe
> ---------------------------------------
>
> Key: TEIIDDES-1508
> URL: https://issues.jboss.org/browse/TEIIDDES-1508
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Debbie Steigner
> Fix For: Komodo
>
>
> Ability to build a VDB pro-grammatically via an API
> The need is to build the VDB during their build process, so would like to pull XMI's into the build process, then bind them together into a VDB for release. This way the build process can choose which version of the XMI files to bundle together into the VDB. Also an addition to this, it would be (almost necessary) great to be able to define what goes into the VDB (roles, translators to use, translator overrides etc) in a file that we can provide to the API, and also that we can check in to our source control.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months