| O/R mapping [message #125] |
Sun, 03 April 2005 17:46 |
Eclipse User |
|
|
|
Originally posted by: eclipse.ambysoft.com
I think that we need to address the following issues clear in the
proposal:
1. The focus is on O/R mapping itself, not the technologies (e.g.
Hibernate, JDO, embedded SQL, ...) used to implement those mappings.
2. We'll need to figure out how to generate the physical mappings
required by the various technologies (e.g. a Hibernate mapping doc)
based on the defined O/R mappings in the Eclipse O/R Mapper (or
whatever it ends up being called).
3. I suspect that we'll need some sort of O/R Mapping validation
plug-in strategy. Each of the O/R mapping technologies have their
strengths and weaknesses and can implement some types of mappings but
not others. For example, some technologies support the ability to map
a class to several tables, some insist on one-to-one mappings. The
point is that we'll need a way to check whether a defined set of O/R
mappings will work given a chosen technology, and if not then to
provide enough information to address the issues appropriately.
4. I've written a fairly comprehensive description of how to do O/R
mapping at http://www.agiledata.org/essays/mappingObjects.html . It
likely isn't complete, but gut feel tells me that it covers 90% or
more of what we need to consider.
- Scott
Scott W. Ambler
www.ambysoft.com/scottAmbler.html
Visit www.agiledata.org for my data writings.
|
|
|
Powered by
FUDForum. Page generated in 0.03699 seconds
Home