Regarding Generators ... not really O/R ... but we've had success with
SQLTags (www.sqltags.org) that uses a generator to produce a java class and
JSP tag for each table defined by the JDBC metadata.  Each tag knows how to
compose an insert, update, and delete statement; provides bean-style access
to each column in the table; provides bean-style access to each parent
foreign and child key for the underlying table. The tags can be nested to
provide master-detail relationships based on the foreign key name-- without
any SQL or JOINS.  SQLTags is currently very early in development, but we
would welcome feedback from anyone who is interested.

--Steve Olson



-----Original Message-----
From: Andrus Adamchik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 11:26 AM
To: Jakarta General List
Subject: Re: Subproject Proposal - crossdb




Fernandez Martinez, Alejandro wrote:

>
> I can imagine why people do their OR tool: because existing ones do not
> fulfill their necessities. In fact, that's what happened to me recently.

Exactly. I haven't seen a decent one so far (except for NeXT/Apple
WebObjects). So if you want to compare O/R with text editors (like it
was done before in this thread), imagine a world with "vi" and "notepad"
  as the only 2 choices. Emacs and MS Word > 6.0 are yet to be invented.

>
> Torque is nice, but you have to specify the database first in the XML.
> Usually, I prefer to code Java instead of XML. If it was the other way
> around, it would have been our primary choice. No flames please: different
> use cases call for different tools. Torque would have been perfect for a
set
> of tables which you can define completely from the beginning, and make a
few
> changes along the way. In our case, the set of tables was meant to grow
and
> be expandable.

This doesn't have to be hard either way. On my last project with
WebObjects, database have grown from 15 to 100 tables along the way (in
about 9 month). With a simple 1 screen GUI tool and a built in class
generator we *never* had problems synchronizing (or rather evolving) the
code base. Products like WebObjects or Cayenne, though they internally
work off of the model file (XML), still make your code easy to change.
But of course this varies from product to product.


--
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
- Andrei (a.k.a. Andrus) Adamchik
Home of Cayenne - O/R Persistence Framework
http://objectstyle.org/cayenne/
email: andrus-jk at objectstyle dot org


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to