[
https://issues.apache.org/jira/browse/DELTASPIKE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605911#comment-14605911
]
Mark Struberg commented on DELTASPIKE-871:
------------------------------------------
Hi Md!
I think this might have nothing to do with DeltaSpike but might be a bug in the
JPA provider you use. Probably you are using an older version? The point is
that the query() is allowed to do a flush. But of course the JPA container has
to properly deal with the state of the entity instance. So this must _never_
result in such a constraint violation.
What exact vendor and versions of your container are you using? Do you have any
sample code to share?
> save() and findByxxx() in same transaction gives constraint violation
> exception
> -------------------------------------------------------------------------------
>
> Key: DELTASPIKE-871
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-871
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
> Affects Versions: 1.2.0
> Environment: Windows-7, Java-8, Netbeans-8.0.2
> Reporter: Md Kamaruzzaman
> Assignee: Daniel Cunha (soro)
>
> It seems like when in the same EJB transaction, save() and findByxxx() is
> called, then delta-spike inserts the entity twice [once in save() and other
> time in findByxxx()] and gives a constraint violation exception.
> After some debuggin, it seems like save() gives a "INSERT" query in DB and
> findByxxx() method calls a flush which again gives the same "INSERT" query in
> DB [INSERT query from save() is not removed from EntityManager] and gives
> constraint violation exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
