[
https://issues.apache.org/jira/browse/JENA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109509#comment-13109509
]
Andy Seaborne commented on JENA-118:
------------------------------------
(not able to test this just at the moment - this is from looking at the code)
Is there an UNLOCK somewhere?
Re: "a bit heavy" -- It seems better to have a safe, working system even if
that incurs some costs. If it's too expensive (unproven), then a better way to
provide the safe usage needs to be found, not remove the locking.
> SDB can't concurrently write (duplicate key error)
> --------------------------------------------------
>
> Key: JENA-118
> URL: https://issues.apache.org/jira/browse/JENA-118
> Project: Jena
> Issue Type: Improvement
> Components: SDB
> Reporter: Damian Steer
> Assignee: Damian Steer
> Attachments: lock-pg.patch
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Multiple concurrent writes in SDB can break because duplicates can appear
> despite the join-based duplicate suppression. Typically the users sees
> something like:
> org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
> constraint "nodes_pkey"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
