Re: Nesting Level - What should I expect when executing after prep


Hi. I am saying you should assume that *any* JDBC code you write
that executes a PreparedStatement (which includes CallableStatements)
will be executed via a stored procedure. If your PreparedStatement
is being asked to execute one of your stored procedures, that stored
procedure will always see the nesting level as > 1.
Your other alternative is to call your procedures with a plain
statement. You would have to send the procedure name and all
it's arguments as a single SQL string.

Joe Weinstein at BEA Systems

.

Relevant Pages

  • Re: Stored procedures being called as Prepared Statements??
    ... When an application executes a PreparedStatement or CallableStatement, ... so that the driver may execute the stored procedure ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: Nesting Level - What should I expect when executing after prep
    ... that executes a PreparedStatement (which includes CallableStatements) ... If any of your stored procedures return output parameters though, ...
    (microsoft.public.sqlserver.jdbcdriver)
  • SqlDataAdapter.Fill returns results of previous command
    ... This code executes successfully at certain points in the application, ... I don't know what the cause of this exception is yet, ... stored procedure was indeed executed on the database. ... The trace shows that the last action on the db was the stored ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Help Isolating Data Access
    ... > I've set up a stored procedure that first queries the table for a record ... > The process that executes this stored procedure runs on multiple threads ... Is there a design pattern for ...
    (microsoft.public.dotnet.general)
  • Re: Tracing user & permissions (triggers and stored p)
    ... To solve my problem I chosed to configure the SQL ... > from xp_cmdshell executes under the security context of the SQL Server ... >> sql Trigger executes a Stored Procedure passing it some variables. ...
    (microsoft.public.sqlserver.security)
Loading