Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346425

Summary: Set the direction for SQL I/O support in EDT
Product: z_Archived Reporter: Matt Heitz <mheitz>
Component: EDTAssignee: Project Inbox <edt.language-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: jshavor
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Matt Heitz CLA 2011-05-19 08:17:59 EDT 
From the I7 planning doc at http://wiki.eclipse.org/EDT:0.7.0_Planning:Iteration_7

data base I/O - needs to be designed, including how JPA will play in, vs straight SQL. In I7, we will target having the direction / design set.
Comment 1 Matt Heitz CLA 2011-06-02 13:57:34 EDT 
JPA is the way to go.

A good initial implementation would be to have the user define all their JPA stuff in Java, and make EGL external types from the POJOs.  (Joe is working on code to make ETs from Java objects.  See 348119.)  EDT would support basic CRUD stuff on the ETs.

Straight SQL can be used alongside JPAs, so adding that capability would be the second step.

Finally, we can support SQL records.  They can optionally include embeds of the ETs for the JPAs, and we'd have to keep track of the relationships.  For example, you could embed an ET for a row of one table, and an ET for a row of another table.  Doing "add rec;" would insert into both tables.  (This is another way of saying an SQL record could be a view.)
Comment 2 Matt Heitz CLA 2011-06-02 13:58:04 EDT 
Closing: Done.
Comment 3 Matt Heitz CLA 2011-06-21 10:26:40 EDT 
Reopening, this needs to be more specific.
Comment 4 Matt Heitz CLA 2011-08-23 16:39:45 EDT 

*** This bug has been marked as a duplicate of bug 355573 ***