Merged
Conversation
…or deletes Using SqlUpdate or an ORM Update query clear the appropriate part of the PersistenceContext. The effect is that ORM queries executed after a bulk update will effectively load a fresh copy of the data from the database and will not reuse an instance from the persistence context if the bean in question had already been loaded.
…sistenceContext Also make improvements to the test asserts in TestPersistenceContextQueryScope
To reflect the behaviour with ebean-orm#3295
…yRequest-readOnly Tidy OrmQueryRequest isReadOnly, just use query.isReadOnly instead
…bean-orm#3319 This change is that findFutureCount, findFutureList, findFutureIds do not trigger a flush on BatchedPstmtHolder. This is to address the possible ConcurrentModificationException that could occur at BatchedPstmtHolder.closeStatements(BatchedPstmtHolder.java:153)
Use Product entity with equals/hashCode implementation added via ebean enhancement
Using clear() and add() when the same id value is used
- Reuse the existing OmBeanListParent and child - Simplify the test setup code - Rename test methods to maybe better reflect what I think is failing Noting that markAsDirty doesn't specifically have anything to do with this bug but it's more on whether the parent bean is dirty or dirty (markAsDirty is just a way to make the parent bean dirty).
… collection' The issue fixed here is a timing one where the parent bean is being updated. The updated parent bean has its internal state reset before the cascade down to the SaveManyBeans where for this case it needs to identify is the 'vanilla' collection has set (via setChildren(new ArrayList()). This fix is a change that for updated beans the dirtyProperties is always obtained and then use this for the isChangedProperty() check.
Adds InsertOptions with ability to control the options used for insert with Postgres around ON CONFLICT.
…test Previous entities are not deleted when replacing OneToMany collection with a new one
…ertOnConflict Add support for Postgres INSERT ON CONFLICT update | nothing
(fix) Future queries do not trigger flush on BatchedPstmtHolder for ebean-orm#3319
…alue) This is the batch size used with PreparedStatement executeBatch() with batched inserts, updates and deletes. 20 is really on the low side and bumping this default to 100 seems good and right.
… clause to use explicit transactions and transaction.addModification()
…n.commit() Remove the deprecated methods: - DB.commitTransaction() - DB.rollbackTransaction() - DB.endTransaction() - database.commitTransaction() - database.rollbackTransaction() - database.endTransaction() Migrate to using try-with-resources and transaction.commit(), transaction.rollback()
…hSize-100 Change default persistBatchSize from 20 to 100 (as a better default value)
…cated-commitTransaction Remove deprecated database.commitTransaction(), migrate to transaction.commit()
Bump ebean-agent, will support future improvement to query beans with…
ebean-orm#3461 - Add also() for query beans
…ns are only on ToMany relationships Changes the query bean code generation for "Associated beans" to have separate AssocOne and AssocMany for *ToOne and *ToMany relationships. Moves the filterMany() expressions such that they are only available on the *ToMany relationships.
…ns are only on ToMany relationships Use protected helper methods on TQAssocBean for the filterMany() methods generated onto AssocMany beans.
ebean-orm#3453 - Different filterMany behavior when no matches found
Paging is an alternative to specifying the maxRows + firstRow + orderBy on a query.
Example:
```java
var orderBy = OrderBy.of("lastName desc nulls first, firstName asc");
var paging = Paging.of(0, 100, orderBy);
DB.find(Contact.class)
.setPaging(paging)
.where().startsWith("lastName", "foo")
.findList();
```
The plan is to migrate OrderBy into an interface
This should never have been public really
Change EmptyPagedList to be deprecated from public use
…service loading bootstrapped services
…eans-improvement ebean-orm#3455 - Improve query beans such that filterMany() expressions are only on ToMany relationships
ebean-orm#3462 Add Paging as alternative to maxRows + firstRow + orderBy
…vice Use io.ebean.service.BootstrapService as common marker interface for service loading bootstrapped services
nulls first isn't supports by mysql
nPraml
commented
Sep 30, 2024
pom.xml
Outdated
| <ebean-datasource.version>8.11</ebean-datasource.version> | ||
| <ebean-agent.version>13.20.1-FOC1</ebean-agent.version> | ||
| <ebean-maven-plugin.version>13.26.0</ebean-maven-plugin.version> | ||
| <ebean-migration.version>13.11.2-FOC2</ebean-migration.version> <!-- Rob: 14.2.0 --> |
nPraml
commented
Sep 30, 2024
| <ebean-migration.version>13.11.2-FOC2</ebean-migration.version> <!-- Rob: 14.2.0 --> | ||
| <ebean-test-containers.version>7.4</ebean-test-containers.version> | ||
| <ebean-datasource.version>9.0</ebean-datasource.version> | ||
| <ebean-agent.version>13.20.1-FOC1</ebean-agent.version> <!-- Rob: 14.6.0 --> |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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.