resultset.last() 在 java 中抛出异常

resultset.last() throws an exception in java

我正在尝试计算 returns oracle BBDD 上的函数的行数。我在其他一些问题中看到(例如:rs.last() gives Invalid operation for forward only resultset : last),需要添加ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY可调用语句.

我试过 ResultSet.TYPE_SCROLL_INSENSITIVE ,也试过 ResultSet.TYPE_SCROLL_SENSITIVE... 没有结果。我仍然得到同样的无效操作异常。

我错过了什么?

这是我的代码:

String call = "{ ? = call MyProcedure (?) }"; 
CallableStatement cstmt= conn.prepareCall(call, ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
cstmt.setString(2,"param 1");
cstmt.registerOutParameter(1, OracleTypes.CURSOR);

cstmt.execute();
ResultSet rset = (ResultSet)cstmt.getObject(1);
rset.last(); //Exception comes here
int rowsnumber = rset.getRow(); 

谢谢。

编辑:

如评论中所述,我首先添加我正在调用的 Oracle 函数:

create or replace FUNCTION MyProcedure
( IdC IN VARCHAR2
)
RETURN sys_refcursor
IS
  c_result sys_refcursor;
BEGIN
  OPEN c_result FOR SELECT name, properties FROM city WHERE name = IdC;
  RETURN c_result;
END;

和堆栈跟踪:

Stack: java.sql.SQLException: Operación no válida para el juego de resultados de sólo reenvío : last
    at oracle.jdbc.driver.InsensitiveScrollableResultSet.last(InsensitiveScrollableResultSet.java:646)
    at MyPackage.CoreWS.ExProcedure(CoreWS.java:58)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:120)
    at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:93)
    at com.sun.xml.ws.server.InvokerTube.invoke(InvokerTube.java:149)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:88)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1136)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:1050)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:1019)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:877)
    at com.sun.xml.ws.server.WSEndpointImpl.process(WSEndpointImpl.java:419)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:868)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:422)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:169)
    at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:229)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:667)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
    at weblogic.wsee.util.ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:108)
    at weblogic.wsee.jaxws.HttpServletAdapter.run(HttpServletAdapter.java:286)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:295)
    at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:128)
    at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:103)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:286)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:260)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:350)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:247)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3679)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3649)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
    at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
    at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
    at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
    at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2433)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2281)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2259)
    at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1686)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1646)
    at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:270)
    at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
    at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
    at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
    at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

仅向前移动其光标的能力是 ResultSet 的默认行为,并且是仅实现 JDBC 1.0 API[ 的驱动程序唯一可能的光标移动=23=]。这种结果集的类型为 ResultSet.TYPE_FORWARD_ONLY,称为仅向前结果集。

如果驱动程序在 JDBC 2.0 核心 API 中实现了光标移动方法,则其结果集可以滚动。可滚动结果集的游标可以向前和向后移动,也可以移动到特定的行。以下方法将游标向后移动到第一行、最后一行、特定行号、当前行的指定行数等:previous、first、last、absolute、relative、afterLast , 和 beforeFirst.

你能确认一下你的API版本吗??

参考:Result set

另外,正如 Mark Rotteveel 在评论中所建议的那样,为什么不将游标作为外参数并显式获取它,而不是在函数中使用 RETURN 并验证它是否正常工作?