Skip to content

Conversation

@vbabanin
Copy link
Member

@vbabanin vbabanin self-assigned this Oct 17, 2025
@vbabanin vbabanin requested a review from a team as a code owner October 17, 2025 20:11
@vbabanin vbabanin requested review from nhachicha and removed request for a team October 17, 2025 20:11
@evergreen-ci-prod
Copy link

There is an existing patch(es) for this commit SHA:

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.

@vbabanin vbabanin requested review from stIncMale and removed request for nhachicha October 17, 2025 20:11
Comment on lines -189 to -206
@Override
public void addBatch(String mql) throws SQLException {
checkClosed();
throw new SQLFeatureNotSupportedException("TODO-HIBERNATE-35 https://jira.mongodb.org/browse/HIBERNATE-35");
}

@Override
public void clearBatch() throws SQLException {
checkClosed();
throw new SQLFeatureNotSupportedException("TODO-HIBERNATE-35 https://jira.mongodb.org/browse/HIBERNATE-35");
}

@Override
public int[] executeBatch() throws SQLException {
checkClosed();
closeLastOpenResultSet();
throw new SQLFeatureNotSupportedException("TODO-HIBERNATE-35 https://jira.mongodb.org/browse/HIBERNATE-35");
}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are not implemented because Hibernate relies on PreparedStatement methods for batching.

@stIncMale
Copy link
Member

stIncMale commented Oct 22, 2025

Let's remove MongoStatement.executeUpdate(String) - Hibernate ORM does not use it. We should do it after dealing with the current PR.

Update: we decided to leave it, as removing it causes code restructuring (otherwise the code looks weird), and we don't want to do that. Continue having this method seems to be a lesser burden than removing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants