[teiid-designer-dev] DDL Importer For Designer

[Ramesh Reddy]

Isn't JPA frameworks generate ANSI DDL? Not sure what you mean by JPA DDL. It may generate DDL using the source specific types. Please correct me if I understood your question wrong.

The way I see it for defining the "source" models SQL DDL (create/alter) is sufficient, however to define the abstraction layer we need extensions to the DDL like SQL/MED to define the transformations. Defining what this can be is currently in discussion in a different thread in teiid-dev list. When we are done defining what this DDL looks like, we would need a DDL importer that can read the above format can represent the DDL is GUI and can write out same DDL with any modifications made back on to disk for consumption by Teiid runtime.

As per the DDL importer didn't Teiid Designer already support a import DDL in its basic from from a text file?

Ramesh..

----- Original Message -----
From: "Barry Lafond" <blafond at redhat.com>
To: "teiid-designer-dev" <teiid-designer-dev at lists.jboss.org>
Sent: Tuesday, August 4, 2009 2:57:26 PM GMT -05:00 US/Canada Eastern
Subject: [teiid-designer-dev] DDL Importer For Designer



All, 

As we're working through assessing integration with other JBoss tools to reconstruct our XML story using annotated POJO's (i.e. Hibernate and JPA) it's become obvious that there will be a potential need in the not-to-distant future to create a DDL'ish importer that can translate Java objects into relational Designer model objects. 

So, if we needed an importer of DDL.... 

1) What would it look like? 

2) What flavor of DDL would we import? (i.e. is JPA-generated ddl sufficient?) Do we want to import "any" DDL and be able to ignore everything except "Create Schema/Table" and Alter statements? 

Barry 

_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev