Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346425 - Set the direction for SQL I/O support in EDT
Summary: Set the direction for SQL I/O support in EDT
Status: CLOSED DUPLICATE of bug 355573
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-19 08:17 EDT by Matt Heitz CLA
Modified: 2017-02-23 14:15 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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 ***