Hibernate version: 3.2.5

Code between sessionFactory.openSession() and session.close():

Name and version of the database you are using: PostgresQL 8.2


I have a bulk update that looks something like "update A set X=:x where B in (:b_list)" (B is a class related by FK). When I execute this, I get an error that essentially says "org.postgresql.util.PSQLException: ERROR: relation "ht_B" does not exist"

After reading through the source code, I think I have found the issue with how the PostgreSQLDialect creates the temporary tables that are used to perform the bulk update. It appears temporary tables are only created once (at Session Factory initialization). In the Postgres dialect, the getCreateTemporaryTablePostfix method returns "on commit drop" -- which I think means "as soon as a commit has occurred on the session, drop this table." So once a commit has happened on the session (including commits having nothing to do with that temporary table), the ht_B table is gone. I think the getCreateTemporaryTablePostfix method should be returning "ON COMMIT DELETE ROWS" so that the temporary tables stay around through the duration.

I looked at a few other dialects -- Oracle uses "ON COMMIT DELETE ROWS". There's even one (TeradataDialect) that says "ON COMMIT PRESERVE ROWS" -- just out of curiosity, what would be the use of that?

Thanks in advance,
Mike Johnson

As a followup, I created a new dialect:



And then ran my logic again with this dialect, and everything seems to work correctly. I am just hoping someone can give me some history as to why the original dialect has "on commit drop" -- there might be something I am missing here!!

If this does indeed need to get fixed, should I file a JIRA issue?

Thanks in advance,
Mike Johnson

I wanted to check again and see if any Hibernate gurus thought this would be a good candidate for a JIRA entry... I'll be happy to enter it if so!

Thanks,
Mike Johnson