Title: [Hibernate] 3.1 rc2
Great
De: [EMAIL PROTECTED]
en nombre de Steve EbersoleEnviado el: vie 14/10/2005
16:41Para: Hibernate developmentAsunto: [Hibernate] 3.1
rc2
So as far as I am concerned, I am ready to push out
3.1rc2. Anythinganyone else wanted to get into this before I cut
Hi,
The "JVM wide system property derby.system.durability to the value true"
does just that (recommended by the Derby crowd).
And it has an effect, but surely not enough; my oracle installation runs
faster.
/max
There maybe some setting we are just missing for test purposes. For
example
There maybe some setting we are just missing for test purposes. For
example, I don't know about you, but on my Oracle setup I disable
recovery logging on the datafiles backing my test schema. Without
disabling this option, it is painfully slow to run the testsuite against
Oracle; and obviously I
#1 - cool, just let me know when you are done.
#2 - is not bubbled up to Query yet. I need to finish some other
refactoring regarding how queries are parsed/cached first. Just follow
HHH-844 and its related cases for the status. Yes, there are
"type-less" setParameter() methods on Query.
AFAIR, the DDL generation fails on my test suite for this DB. They are
too strict in some are. So unless they've relaxed some restriction, it's
a nope for me.
Max Rydahl Andersen wrote:
Hi,
A small FYI crosspost here since both communities has talked about it.
Tonight I tried out Derby and
Hi,
yes - there is alot more "weird" limitations, but Derby is not alone in
that
aspect (db2 comes to mind ;) But the turnaorund performance is
disappointing.
/max
AFAIR, the DDL generation fails on my test suite for this DB. They are
too strict in some are. So unless they've relaxed s
1. I want to add a new operation persistOnFlush
Remember why we did introduce the PERSIST_ON_FLUSH cascading action? For
EJB3 flush efficiency
In the current impl, it is only used for the first level of flushing in
EJB3 (ie action inherited from FlushEventListener.getCascadingAction()
To workar
