sounds reasonable IFF the db doesn't get stupid and does 20 lookups for
duplicate id's.
/max
Currently we create several loaders following a certain algorithm
Why don't we create a single loader of batch-size and duplicate ids in
the in clause to match unfilled parameters
batch-size = 2
In xml to set up a filter on the target table of a many to many, you set
the filter element inside the element
To support that in annotations, I could do
1.
@Filter (pointing to the association table or the target table if a
@OneToMany @JoinColumn)
@FilterManyToMany (@FilterTargetEntity) (poi
On Sep 28, 2006, at 8:51 PM, Emmanuel Bernard wrote:
@Filter (pointing to the target table)
@FilterJoinTable (pointing to the association table)
I like 2. better, it is more consistent esp when you realize that
@OneToMany can use a join table just by changing an annotation.
2. would require
Done and committed
@Filter(s) applies to the target entity table
@FilterJoinTable(s) applies to the association table
in a symmetric way
@Where applies to the target entity table
@WhereJoinTable applies to the association table
If the book can still be updated...
Christian Bauer wrote:
On Sep
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sqlserver-jtds-testsuite?log=log20060928223450
BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 09/28/2006 22:34:50Time to build: Last changed: 12/31/2005 20:44:14Last log entry: less noisy
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20060929022143
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/sc
