Hmmm, my bad. I merged the branch manually and that didn't remove the PR so I've merged this twice now and hence ended up with a duplicate method. All good, just removing this duplicate method.
Example:
One X can have many Ys. Ys can be soft deleted.
Y1 -> X1 -> Y1
Y1 is soft deleted
When Y1 is loaded, lazy-loading X1 and then lazy-loading the list of Ys associated with X1,
the list should contain Y1. This test asserts that is true.
Example:
One X can have many Ys. Ys can be soft deleted.
Y1 -> X1 -> Y1
Y1 is soft deleted
When Y1 is loaded, lazy-loading X1 and then lazy-loading the list of Ys associated with X1,
the list should contain Y1. This test asserts that is true.
When a child is referenced in the query, Ebean should make sure
that the child (or any of the objects connecting it in the query)
is deleted.
Ie. if a query requires a child to have a certain value, it should
filter out those children that are soft deleted. It should also perform
the deleted check on all objects leading up to that child.
E.g. assuming that all objects are soft deletable, the following where():
DB.find(Alpha.class).where()
.eq("alpha.beta.gamma.name", "bar")
should generate a query with
"t0.deleted = false AND t1.deleted = false AND t2.deleted = false AND t2.name = 'bar'"
* ADD: failing testcase for orderColumn when tree depth > 1
* FIX: no update with @OrderColumn on treeDepth > 1 and avoid needless updates
* ADD: failing testcase for removing models in oneToMany relation with @OrderColumn
Signed-off-by: Jonas Pöhler (JPo) <jonas.poehler@foconis.de>
* ADD: failing test for faulty element reordering in a entityBean tree with version
Signed-off-by: Jonas Pöhler (JPo) <jonas.poehler@foconis.de>
* FIX: incorrect behaviour when reordering or removing elements from collection with @OrderColumn.
Signed-off-by: Jonas Pöhler (JPo) <jonas.poehler@foconis.de>
* ADD: failing testcase for "insert into table default values;" is invalid MySql syntax
* FIX: "insert into table default values;" is invalid MySql syntax
* #1970 - Change test code only moving mapping annotations to fields
First step in remove support for mapping annotations on "Getters" (so field only target for mapping annotations)
* #1970 - Remove reading mapping annotations from "Getters"
* #1970 - Refactor to use simple annotation lookup where possible
* #1970 - Remove GenerationType.TABLE and SequenceGenerator from type/class
* #1970 - Refactor meta annotation reading
* #1970 - Read @Aggregation as a meta annotation
rob bygrave