I talked to Strong this morning and created
https://hibernate.onjira.com/browse/HHH-6731
I've updated the JIRA to include looking into
InvalidatedTransactionalTestCase.testEvict
Cheers,
On Oct 13, 2011, at 12:43 AM, Sanne Grinovero wrote:
> Steve,
> as I was saying in chat if this failing tes
hey guys,
i'm currently facing the following situation:
we're using the current stable version of hibernate (3.6.7) as a jpa-vendor
with an oracle database. the ids of our entities are generated by a sequence,
which works fine. but in the case of a failure during the save action, our
entities
Check out hibernate.use_identifier_rollback in the doc.
Also please use the user forum for such questions. This is the hibernate
development mailing list.
Emmanuel
On 14 oct. 2011, at 18:10, Marcel Hörr wrote:
> hey guys,
>
> i'm currently facing the following situation:
>
> we're using the c
In [1], I am seeing the following type mappings:
Column type: LONG -> java.sql.Types.LONGVARCHAR -> java.lang.String
Column type: LONGRAW -> java.sql.Types.LONGVARBINARY -> byte[]
org.hibernate.type.TextType is consistent with the mapping for LONG.
org.hibernate.type.ImageType is consistent with
How does this impact existing applications? Would they have to convert
LONGs to CLOBs (and LONGRAWs to BLOBs) to keep the application working?
As far as the advantage of CLOB over TEXT, if you read every character,
which one is really faster? I would expect TEXT to be a little faster,
since t
