[
https://issues.apache.org/jira/browse/OPENJPA-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-2998.
--------------------------------------
Resolution: Fixed
Addressed on master: TestBatchLimitException keeps the isMariaDB flag, gated by
the dictionary (MariaDBDictionary), and the comment now names the versions
observed - MariaDB 11.8 with Connector/J 3.5.4 reports the first row of a
failing batch as the failed object (like Oracle/Postgres), while earlier
Connector/J and 11.4 combinations were per-row. The branch therefore no longer
accepts either message, so a future regression on a given version combination
would still be caught.
> MariaDB branch accepts either message without naming versions
> -------------------------------------------------------------
>
> Key: OPENJPA-2998
> URL: https://issues.apache.org/jira/browse/OPENJPA-2998
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 4.2.0
> Reporter: Maxim Solodovnik
> Priority: Major
> Fix For: 4.2.0
>
>
> Discussion thread:
> https://github.com/apache/openjpa/pull/144#discussion_r3683007909
> **(low)** The MariaDB branch now accepts either the per-row or first-row
> failed object/message "across versions", weakening the exact-match check
> still applied to other DBs. If specific MariaDB versions differ, could the
> comment name the versions observed so this does not quietly absorb future
> regressions?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
