Update to head #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…"parent" rather than copy beans (adjustment of #2021)
…xplicit cast / using clause.
…rly handle server timezone
… database platform being used
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'"
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.
…hen query has predicates on a ToMany path the associated soft delete predicates are not included)
…-/ebean into tobias--soft_deletes_not_included
…remember includeSoftDeletes
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.
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.
- Move ScalarType, DataBinder, DataReader, ExtraTypeFactory to ebean-core-type module - Update the ebean-postgis and other modules
Refactor extract ebean-core-type module moving ScalarType and related interfaces to io.ebean.core.type
…reType - Rename ModifyAwareOwner to ModifyAwareType - Move to io.ebean (making it properly public) - Remove the requirement for Serializable - Simplify to effectively a getter/setter pair (dirty state flag) - Simplify to reset the dirty state flag via
…tgres - Use NO KEY with FOR UPDATE clauses
Signed-off-by: Jonas Pöhler (JPo) <[email protected]>
- Changes to generally not close BatchedPstmt on executeBatch() and instead closed on commit/rollback
#2089 - Postgres - Use NO KEY with FOR UPDATE clauses with Postgres
Refactor io.ebeaninternal.json.ModifyAwareOwner to io.ebean.ModifyAwareType
…moteTableMod or remoteCacheEvent
Add support for Postgres lock types (no key, share, key share) with FOR UPDATE
Rename PlatformConfig.defaultLockWithKey to PlatformConfig.forUpdateNoKey
…batch_flush 2110 - Fix and test for executeBatch() on SqlUpdate
Slightly improve the name of the enum. Note that although this is on public Query it's only internally used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.