Jeff Watkins wrote:
Ronald Jaramillo wrote:
Hi,
Ian has a point there, one of the reason Hibernate is doing so much,
is partly because writing logic in Java is not as fun as doing it in
Python, so doing as much as possible in a declarative way is
reasonable in the J2EE world.
Except that selectBy always hits the Database and doesn't seem to cache
the results. This is similar to the problem with alternate ID columns:
when you request something by an alternate ID, you're doing query even
if the object is already in memory -- at least that's what I've been
able to figure out.
Caching is a separate concern, and I think it's bad to mix that into
what-is-possible discussions. Caching is an optimization; though an
important optimization (sometimes), premature consideration of
optimizations is not good for design. Plus it sounds like you are
trying to find new reasons not to like our answers ;)
SQLObject certainly isn't J2EEish, in a whole bunch of ways. Personally
I think that's okay; and one some level you must think so too, since you
are here after all.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
