[
https://issues.jboss.org/browse/ARTIF-713?page=com.atlassian.jira.plugin....
]
Brett Meyer closed ARTIF-713.
-----------------------------
Resolution: Won't Fix
For completeness, here's why this should never happen (forgot when I opened it):
Persisting artifact A happens in one transaction, while querying for artifacts to
potentially target with a relationship owned by A happens in another transaction. In
order to allow items in a batch to be related to *each other*, the transaction needs to
be committed after each item is persisted. Otherwise, the latter transaction isn't
able to see it.
Being able to support this would be extremely complicated and, ultimately, could require
holding quite a bit of info in memory during batch execution.
Persist each batch upload with one single transaction
-----------------------------------------------------
Key: ARTIF-713
URL:
https://issues.jboss.org/browse/ARTIF-713
Project: Artificer
Issue Type: Sub-task
Reporter: Brett Meyer
Assignee: Brett Meyer
Currently, each *item* in a batch is handled by a separate JDBC transaction. Instead, it
would be far more performant to commit the *entire* batch in a single transaction.
Further, from a user perspective, this setup makes more sense anyway...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)