Re: [teiid-designer-dev] 7.0 Dev Plans

+1 for idea of building as a plug-in that is separate from any dependencies from the rest of the Designer. This way this functionality will truly become a plugin that can be only activated when the Container is configured to work with JB Tools. What is a Athena build? private repos? What about using branch? Ramesh.. On Fri, 2010-01-29 at 16:35 -0500, John Doyle wrote: > Hey Barry, > > In an earlier thread(http://lists.jboss.org/pipermail/teiid-designer-dev/2010-January/0... we talked about integrating the DTP stuff for 7.1. The doc you just put up (http://community.jboss.org/wiki/TeiidDesigner70DevelopmentPlans) says we're going to "Modify DQP/SQL Explorer plugins to execute VDB via DTP's jdbc connection to Teiid." I'd like to clarify what this means. > > The work I have done so far with DTP enables a user to do the following in the DTP perspectives. > 1) Create connections to Teiid (6.X only for now, but 7.0 should only be minor tweaks because it's just a JDBC connection). > 2) View the metadata for the VDB. > 3) Use the DTP graphical SQL statement building tools to create queries. > 4) Execute SQL statements on the VDB and view results. > > I have a suggestion from Steve H that I need to test out that will allow me to integrate the DTP query plan view capability also. > > I would like to target the DTP related work to 7.0. Specifically, get rid of the SQL Explorer plugins and execute VDBs via DTPs perspectives. As it is there are a a lot of unknowns in what we're taking on for 7.0, so maybe I'm trying to bite off too much. What do you think? > > > On a related issue, the DTP code is currently in my private repos, and I was working on an Athena build for it. I thought it would be a good idea to build it as it's own feature so that a non-Designer user of Teiid (someone building a web app on the VDB for instance) could download it without a dependence on Designer, and it could also be built into Designer. To that end I was figuring it could live in the JBTools repos. We can discuss this part on another thread I suppose as its a different issue. > > ~jd > > > > _______________________________________________ > teiid-designer-dev mailing list > teiid-designer-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/teiid-designer-dev _______________________________________________ teiid-designer-dev mailing list teiid-designer-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-designer-dev