[
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643223#comment-14643223
]
Harald Wellmann commented on DELTASPIKE-965:
--------------------------------------------
Ok, I pushed my fix. Not quite sure yet if this is the best solution, but at
least it fixes a showstopper, and we can further improve on it.
As far as I can see, this issue is a showstopper for anyone using the Data
module with entities containing a String ID which is not generated, so I'm a
bit surprised nobody else ran into the problem yet...
I bumped into it when trying to upgrade my daytime project to from 1.3.0 to
1.4.2 this morning (just another manic Monday...). As a workaround, I
downgraded to 1.4.1, but I'd really like to see a 1.4.3 release with a fix
rather soon.
> EntityRepository.save() is broken for entities with String ID
> -------------------------------------------------------------
>
> Key: DELTASPIKE-965
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-965
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
> Affects Versions: 1.4.2
> Reporter: Harald Wellmann
> Assignee: Daniel Cunha (soro)
> Priority: Blocker
> Fix For: 1.4.3
>
>
> EntityRepository.save() generates illegal SQL when the entity identity is of
> String type.
> This is a regression introduced in 1.4.2 with
> {{org.apache.deltaspike.data.impl.handler.CdiQueryInvocationContext.countCheck(Object)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
