"If someone asks you to do something you don't know how to, don't tell I don't know, tell I can learn instead." - Myself
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
... you could use JPA's native query.
What benefit would JPA provide here?
"If someone asks you to do something you don't know how to, don't tell I don't know, tell I can learn instead." - Myself
Originally posted by Edisandro Bessa:
So you are telling that JPA has a feature called "native query" where I can submit stored procedure calls ? (Depending of database support of course)
benefits of JPA's connection pool manager and transactions, which are transparently managed by API, instead of hard controlling transactions by ourselves as we have done so far.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
James Sutherland wrote:Yes, you need to set returnsResultSet=false if you want the query to return the output parameter values. If you set it to true, then it is assumed that the procedure will return a ResultSet, and the result set value will be returned (an outputParametersDetected event would be raised for any output parameters).
Don't get me started about those stupid light bulbs. |