I had IRC conversation with Steve Ebersole about adding the Teiid Dialect to the Hibernate Core in the next upcoming 3.5 release. He is not willing to accept any dialects that are not testable from their testing framework. He said Hibernate uses a schema export tool that issues some DDL queries through JDBC interface for their testing to work. Since Teiid driver does not support the DDL currently, issuing the DDL is not possible. He suggested that we look into ways to 1) delegate the DDL calls either through the TeiidDriver (https://jira.jboss.org/jira/browse/TEIID-669) or 2) devise a way in their schema export tool to delegate the DDL class. also, since they already have two CR releases, chances of getting into 3.5 release seems slim. However, if we can make it that would be great. Any suggestions? volunteers? Thanks. Ramesh.. On Tue, 2010-03-23 at 13:05 -0500, Ramesh Reddy wrote: > I am not dis-agreeing. Just wanted to what our options were. > > I do think it is valuable for Teiid be included along with Hibernate. > They are about to release 3.5 very soon, we need to see if we can make > it into 3.5 final release. > > So, instead of making this JIRA in the Tools, we need to make this into > Hibernate by communicating with its lead. > > > Thanks > > Ramesh.. > > On Tue, 2010-03-23 at 11:01 -0400, John Doyle wrote: > > Ramesh-The drivers are supplied by the DataTools ConnectionProfiles > > and Drivers that you have to define before you use Hibernate, so > > drivers are a different issue, and not something that the hibernate > > plug-ins have 'built in'. It's an configuration step that's already > > extensible in a way that Dialects don't appear to be. > > > > I'm personally in favor of including our dialect in Hibernate because > > then Tools will just work, there won't be some additional step for > > Teiid. It seems to me that if Oracle just works out of the box in > > Tools, then a fellow JBoss project should just work. The only > > downside I can see to including our dialect in Hibernate is that our > > release cycles don't match up and changes/maintenance would have to be > > managed across our differing cycles. > > _______________________________________________ > teiid-dev mailing list > teiid-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/teiid-dev _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev