Re: [eclipselink-users] Exception when calling entityManager.remove: The

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipselink-users] Exception when calling entityManager.remove: The parameter name [version] in the query's selection criteria does not match any parameter name defined in the query

From: Martin Vojtek <martin.vojtek@xxxxxxxxxx>
Date: Sun, 7 Sep 2014 07:48:30 -0700 (PDT)
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

At the first sight it should work. I haven’t used this type of mapping before. Maybe you can file a bug into bugzilla for this case.

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EclipseLink

Martin

From: Andreas Joseph Krogh [mailto:andreas@xxxxxxxxxx]
Sent: 7. září 2014 16:35
To: eclipselink-users@xxxxxxxxxxx
Subject: Re: [eclipselink-users] Exception when calling entityManager.remove: The parameter name [version] in the query's selection criteria does not match any parameter name defined in the query

På søndag 07. september 2014 kl. 16:26:56, skrev Martin Vojtek <martin.vojtek@xxxxxxxxxx>:

Hi Andreas,

You are probably using optimistic version locking.

http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Basic_JPA_Development/Mapping/Locking/Optimistic_Locking

You can use pessimistic locking or add version column to BudgetGroup object.