5:28 a.m.
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6.0, 3.6.0.CR2, 3.6.0.CR1, 3.5.6,
3.6.0.Beta4, 3.6.0.Beta3, 3.5.5, 3.6.0.Beta2, 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1,
3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2,
3.5.0.Beta-1
Reporter: gwa
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
gwa commented on HHH-6280:
--------------------------
I've forgot to mention that the problem come from the
org.hibernate.ejb.criteria.expression.LiteralExpression class
in the render method, the code :
{code:java}
if ( ValueHandlerFactory.isNumeric( literal ) ) {
return ValueHandlerFactory.determineAppropriateHandler( (Class)
literal.getClass() ).render( literal );
}
{code}
return directly the value of the expression instead of creating a binded parameter.
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.0.Beta-1, 3.5.0-Beta-2, 3.5.0-Beta-3, 3.5.0-Beta-4, 3.5.0-CR-1,
3.5.0-CR-2, 3.5.0-Final, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.6.0.Beta1, 3.6.0.Beta2, 3.5.5,
3.6.0.Beta3, 3.6.0.Beta4, 3.5.6, 3.6.0.CR1, 3.6.0.CR2, 3.6.0, 3.6.1, 3.6.2, 3.6.3, 3.6.4
Reporter: gwa
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:31 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
William Ashley commented on HHH-6280:
-------------------------------------
Since the other ticket is closed I'll use this one.
There's another side effect of this behavior which nobody has pointed out: it bypasses
any UserType that might be in place for the property. So in a way, all LiteralExpressions
against numeric UserType'ed properties are broken. I ran into this today for a
property of type long that maps, via a UserType, to BINARY in the database. The workaround
is to use a ParameterExpression, but this is pretty messy and hopefully a future version
of hibernate will address it.
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.0.Beta-1, 3.5.0-Beta-2, 3.5.0-Beta-3, 3.5.0-Beta-4, 3.5.0-CR-1,
3.5.0-CR-2, 3.5.0-Final, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.6.0.Beta1, 3.6.0.Beta2, 3.5.5,
3.6.0.Beta3, 3.6.0.Beta4, 3.5.6, 3.6.0.CR1, 3.6.0.CR2, 3.6.0, 3.6.1, 3.6.2, 3.6.3, 3.6.4
Reporter: gwa
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:13 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Steve Ebersole updated HHH-6280:
--------------------------------
Suitable for new contributors: [Yes, likely]
Affects Version/s: (was: 3.6.3)
(was: 3.6.2)
(was: 3.6.1)
(was: 3.6.0)
(was: 3.5.6)
(was: 3.6.0.CR1)
(was: 3.6.0.Beta4)
(was: 3.6.0.Beta3)
(was: 3.6.0.Beta2)
(was: 3.6.0.CR2)
(was: 3.5.4)
(was: 3.5.3)
(was: 3.5.2)
(was: 3.5.0-Final)
(was: 3.5.1)
(was: 3.5.0-CR-1)
(was: 3.5.0-Beta-4)
(was: 3.5.0-CR-2)
(was: 3.5.0-Beta-3)
(was: 3.5.0-Beta-2)
(was: 3.6.0.Beta1)
(was: 3.5.0.Beta-1)
Fix Version/s: 4.0.0.next
Assignee: Steve Ebersole
Labels: jpa2 (was: )
There was a reason I ended up keeping numerics as literals in the SQL. But to be honest I
forget the reason at the moment. We can discuss this though. I am not for or against it
totally. Initially my hope was to have all the criteria literals be transformed into
parameters.
@William, there is a flip side to this argument. Some databases rely on the values being
literals for certain optimizations to be triggered. On Oracle for example if you want the
optimizer to select from a partition that will only be optimized as such if the partition
value is a literal. Yes the general case is that you would want these to get
parameterized; but the drawback is that there is no work around then for the cases where
you really want them as literals.
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:11 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
William Ashley commented on HHH-6280:
-------------------------------------
A couple of ideas off the top of my head:
- Literal expressions could be parameterized if the underlying property is mapped with a
UserType (or otherwise isn't transformed between Java and SQL)
- Perhaps this inlining optimization should have to be explicitly activated by some sort
of property-level metadata (a hibernate-specific annotation would probably be required)
Thoughts?
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:16 p.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
William Ashley edited comment on HHH-6280 at 8/20/11 8:15 PM:
--------------------------------------------------------------
A couple of ideas off the top of my head:
- Literal expressions could be parameterized if the underlying property is mapped with a
UserType (or otherwise is transformed between Java and SQL)
- Perhaps this inlining optimization should have to be explicitly activated by some sort
of property-level metadata (a hibernate-specific annotation would probably be required)
Thoughts?
was (Author: washley):
A couple of ideas off the top of my head:
- Literal expressions could be parameterized if the underlying property is mapped with a
UserType (or otherwise isn't transformed between Java and SQL)
- Perhaps this inlining optimization should have to be explicitly activated by some sort
of property-level metadata (a hibernate-specific annotation would probably be required)
Thoughts?
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Steve Ebersole commented on HHH-6280:
-------------------------------------
I almost always use the {{Type}} interface directly when implementing custom types. So
trying to distinguish based on {{instanceof UserType}} is not a good approach. Good
thought, I just know its not going to work.
So iirc the issue that lead me to use literals here had to do with scale and operations.
Meaning (again, iirc) some databases needed to know type information to be able to
properly handle something like {{... ? + ? ...}}, etc. So the choice was to either wrap
all such params in {{CAST}} function calls and hope/pray the db implemented a proper
{{CAST}} function or use literals. In the end I opted for the literal route because,
well, thats what the user asked for up front. Wrapping in function calls will limit the
databases ability to leverage indexes in quite a few databases.
Gonna move this to the next release so we can discuss this some more.
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Steve Ebersole updated HHH-6280:
--------------------------------
Fix Version/s: (was: 4.0.0.CR2)
4.0.0.next
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Steve Ebersole updated HHH-6280:
--------------------------------
Fix Version/s: (was: 4.0.0.CR4)
4.0.0.next
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Gail Badner updated HHH-6280:
-----------------------------
Fix Version/s: (was: 4.0.0.CR5)
4.0.0.next
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Steve Ebersole updated HHH-6280:
--------------------------------
Fix Version/s: (was: 4.0.0.CR6)
4.0.0.next
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Strong Liu updated HHH-6280:
----------------------------
Fix Version/s: (was: 4.0.0.CR7)
4.0.0.next
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.0.next
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:24 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Steve Ebersole updated HHH-6280:
--------------------------------
Fix Version/s: (was: 4.0.0.Final)
4.0.1
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.4
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
Fix For: 4.0.1
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:12 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6280) JPA criteria API don't bind numeric field
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280?page=c...
]
Steve Ebersole updated HHH-6280:
--------------------------------
Affects Version/s: (was: 3.6.4)
Fix Version/s: (was: 4.0.1)
Unscheduled as this needs more discussion and so far it has been a monologue :)
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6280
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6280) JPA criteria API don't bind numeric field
[
https://hibernate.onjira.com/browse/HHH-6280?page=com.atlassian.jira.plug...
]
Strong Liu commented on HHH-6280:
---------------------------------
https://issues.jboss.org/browse/JBPAPP-7198
JPA criteria API don't bind numeric field
-----------------------------------------
Key: HHH-6280
URL: https://hibernate.onjira.com/browse/HHH-6280
Project: Hibernate ORM
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5
Reporter: gwa
Assignee: Steve Ebersole
Labels: jpa2
When you use JPA criteria API, the numeric value are not binded but are directly set in
the SQL instead.
eq: you have a generated SQL like:
select ... from ... where age=12;
instead of
select ... from ... where age=?;
With '12' as parameter.
when you test the following code:
{code:java}
@Entity
public class User {
@Id
private int id;
private int age;
...
}
{code}
{code:java}
CriteriaBuilder builder=em.getCriteriaBuilder();
CriteriaQuery<User> query=builder.createQuery(User.class);
Root<User> root=query.from(User.class);
query.select(root).where(builder.equal(root.get("age"),12));
em.createQuery(query).getResultList();
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4301
days inactive
4782
days old
hibernate-issues@lists.jboss.org
23 comments
6 participants
participants (6)
-
Brett Meyer (JIRA) -
Gail Badner (JIRA)
-
gwa (JIRA)
-
Steve Ebersole (JIRA)
-
Strong Liu (JIRA)
-
William Ashley (JIRA)