I'm having a little issue with the new prepared statement cache. I wrote
a wrapper class for PreparedStatements to simplify way they are checked
in and out of the cache. Unfortunately, the JDK1.4 PreparedStatement
interface declares a method of type java.sql.ParameterMetadata. This
class doesn't ex
I've just finished the two refactoring tasks I indicated were necessary
for the collection cache. What I've done is:
(1) given the ScheduledX classes an
afterTransactionCompletion()
method so that they can release any cach softlocks they acquired from
the execute() method.
(2)
>I think the native keygenerator should have a parameter where you can
>specify the sequence name, and if its really a sequence that one is
>used.
okay. done. I havn't added a seperate "identity" style but I'll get
onto that later. For now, "native" allows "sequence" as a fallback.
--
>At the point a collection is loaded from the database, Hibernate should
>disassemble each object in the collection and store that either with the
>collection's owner's cached value or in a cache in the collection's
>CollectionPersistor.
>
>Is that correct?
yes. essentially correct.
After the c
