Tom, Frank,
> I do not recall hearing from any satisfied users of
> Hibernate-on-Postgres before ... in fact I never heard of Hibernate
> before ... so call me clueless if you like, but a few rough edges in the
> interface don't seem too implausible from here.
Actually, I have a client using Hibernate, and they've not had a problem with
it. I'm no java expert (I hire those), but I was favorably impressed with
the software --and with its level of compatibility with PostgreSQL.
Not so Jakarta. Every client we've had using Jakarta has required help from
a pg-JDBC expert in debugging and configuration; apparently the way Jakarta
comes "out of the box" is barely usable with PG. So this is a possible
source of problems.
Frank, from you description of your problems, I can see only 2 possibilities:
1) You are not connecting to the database you think you are. Possibly you're
still connecting to "test"? Or different parts of the system have their own
connection info?
2) Some part of your stack, due to configuration issues, is opening
transactions for each batch of DML statements and not closing them. These
non-committed statements, of course, would be automatically rolled back on a
database restart or after connection termination. This is a problem I've
seen on *lots* of Java applications.
--
Josh Berkus
Aglio Database Solutions
San Francisco