-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

View unanswered posts | View active topics


Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]


Forum locked This topic is locked, you cannot edit posts or make further replies.  Page 1 of 1
  [ 2 posts ] 
  Previous topic | Next topic 
Author Message
robnik
 Post subject: Upgrading 3 to 5.2, setParameter goes from 0 to 1 based?
PostPosted: Fri May 05, 2017 3:24 pm 
Newbie

Joined: Fri May 05, 2017 12:09 pm
Posts: 7
I had a bunch of code like:

Code:
SQLQuery q = session.createSQLQuery("select a,b,c from t where a < ?")
q.setParamater(0, ...)


The SQLQuery is deprecated in favor of NativeQuery, but after replacing "SQL" with "Native" above, now I get errors like: Unknown parameter position: 0

Is there a global config somewhere for this, or do I need to adjust all my integers up by one when moving to the NativeQuery class?

thanks,
Rob
Top
 Profile  
 
vlad
 Post subject: Re: Upgrading 3 to 5.2, setParameter goes from 0 to 1 based?
PostPosted: Fri May 05, 2017 4:09 pm 
Hibernate Team
Hibernate Team

Joined: Thu Sep 11, 2014 2:50 am
Posts: 1628
Location: Romania
Native Query is JPA-specific, and just like JDBC the position starts at 1. You are better off using named parameters instead.
Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  Page 1 of 1
  [ 2 posts ] 

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.