Αποτελέσματα Αναζήτησης
V$SQL_BIND_CAPTURE displays information on bind variables used by SQL cursors. Each row in the view contains information for one bind variable defined in a cursor. This includes:
V$ALL_SQL_BIND_CAPTURE allows application developers to view information about their own bind variables used by SQL cursors. It is similar to the V$SQL_BIND_CAPTURE view, with the following exception:
2 Ιουν 2023 · Bind variables, often called bind parameters or query parameters, are often used in WHERE clauses to filter data. Instead of putting the required value into the query, or writing separate queries for each different value, or concatenating strings, you can use bind variables. Here’s how it works.
V$SQL_BIND_DATA describes, for each distinct bind variable in each cursor owned by the session querying this view: Actual bind data, if the bind variable is user defined. The underlying literal, if the CURSOR_SHARING parameter is set to FORCE and the bind variable is system generated.
24 Ιουλ 2008 · select b.sql_text, a.bind_vars, c.datatype, c.value from v$sql_cursor a, v$sql b, v$sql_bind_data c where b.address = a.parent_handle and a.curno = c.cursor_num and b.sql_id= '&v_sqlid' and b.child_number = &v_sqlcn /
18 Οκτ 2010 · In Oracle 11.2, if you have the Diag+Tuning Pack licenses and the SQL monitoring kicks in for your SQL statement, then instead of the old fashioned ERRORSTACK dump reading you can just query the V$SQL_MONITOR.BIND_XML to find the values and metadata of your SQL statement’s bind variables.
Concatenating variable values into a SQL statement makes the statement unique, forcing a hard parse. By contrast, using bind variables allow reuse of statements as the text of the statement remains the same. Only the value of the bind variable changes.
