iddlmZmZmZmZddlmZddlmZddlm Z ddl m Z ddl m Z mZddlmZdd lmZdd lmZGd d e ZGddeZGddeZdS))AnyUnionCallableOptional) connection)errors)utils) BaseMetaClass)DbTypeDB_TYPE_OBJECT) DbObjectType) FetchInfo)VarceZdZdZ dJdddeddfdZdZd Zd Zd Z dKd e d e e e fdededdf dZ dKd e d e e e fdede ddf dZdee dee fdZ dLde de deddfdZ dKdZdMdZdMdZedefdZejdeddfdZ dNde eeefde e efd edefd!Z de fd"Z!ede fd#Z"dMd$Z#ede e e$dffd%Z%ede fd&Z&de fd'Z'de fd(Z(de fd)Z)ede*fd*Z+e+jde*ddfd+Z+ede fd,Z,ede*fd-Z-e-jde*ddfd.Z-edefd/Z.e.jdeddfd0Z. dLde de deddfd1Z/edefd2Z0ede*fd3Z1e1jde*ddfd4Z1edefd5Z2e2jdeddfd6Z2d7ed8ede e effd9Z3dNd ed:eddfd;Z4ede e dffd<Z5 dOdd>de eeefd ed?ed@e*dAe*dBe dCe dDedEedFe ddGfdHZ6ede e7j8dffdIZ9dS)P BaseCursorNFrconnection_module.Connection scrollablereturncR||_|j||_dSN) _connection_implcreate_cursor_impl)selfrrs _/var/www/html/Pagina-Ingenieria-Requisitos/venv/lib/python3.11/site-packages/oracledb/cursor.py__init__zBaseCursor.__init__/s( &%88DD cN|j|jddSdS)NTin_del)rclosers r__del__zBaseCursor.__del__7s1 : ! J  D  ) ) ) ) ) " !rc.||SzY The entry point for the cursor as a context manager. It returns itself.  _verify_openr#s r __enter__zBaseCursor.__enter__;s  rcr||jdd|_dSzc The exit point for the cursor as a context manager. It closes the cursor. Tr Nr(rr")rexc_type exc_valueexc_tbs r__exit__zBaseCursor.__exit__Bs:  %%% rc6|jj}d|d|jdS)N) __class__ _public_namer)rcls_names r__repr__zBaseCursor.__repr__Ks'>.58555555rname parameterskeyword_parameters return_valuectj||||||||\}}|||S)zn Internal method used for generating the PL/SQL block used to call stored procedures. )r verify_stored_proc_argsr(_call_get_execute_argsexecute)rr8r9r:r; statement bind_valuess r_callzBaseCursor._callOsd %j2DEEE !%!z5BaseCursor._call_get_execute_args..vs JJJa%1q5/JJJrz => :r,z); end;)appendextendrangelenitemsjoin) rr8r9r:r; bind_namesrAstatement_partsarg_name arg_valuer@s rr>z!BaseCursor._call_get_execute_argsasX  #*  #  " "= 1 1 1   | , , ,tcz***  K   z * * *JJ5Z3I3IJJJJ  K'9'?'?'A'A K K#)""9---!!X"I"IC OOa4G"I"IJJJJsxx 33444y)))GGO,, ;''rr@cr|4|}|stjtj|S)z Normalizes a statement by stripping leading and trailing spaces. If the result is an empty string, an error is raised immediately. )stripr _raise_errERR_EMPTY_STATEMENTrr@s r_normalize_statementzBaseCursor._normalize_statements;  !))I >!&"<===rTtagcache_statementc>|j|||dS)zO Internal method used for preparing a statement for execution. N)rpreparerr@r]r^s r_preparezBaseCursor._prepares$ 9c?;;;;;rc||j|||||dS)zJ Internal method for preparing a statement for execution. N)r(r_prepare_for_executer\)rr@r9r:s rrdzBaseCursor._prepare_for_executesT  ''   % %i 0 0        rc||j|s tjtjdSdS)zF Verifies that fetching is possible from this cursor. N)r(ris_queryr rYERR_NOT_A_QUERYr#s r _verify_fetchzBaseCursor._verify_fetchsR z""4(( 6  f4 5 5 5 5 5 6 6rc|jtjtj|jdS)z Verifies that the cursor is open and the associated connection is connected. If either condition is false an exception is raised. N)rr rYERR_CURSOR_NOT_OPENr_verify_connectedr#s rr(zBaseCursor._verify_opens: :   f8 9 9 9 ))+++++rcB||jjS)a This read-write attribute can be used to tune the number of rows internally fetched and buffered by internal calls to the database when fetching rows from SELECT statements and REF CURSORS. The value of ``arraysize`` can drastically affect the performance of a query since it directly affects the number of network round trips between Python and the database. For methods like :meth:`fetchone()` and :meth:`fetchall()` it affects internal behavior but does not change how many rows are returned to the application. For :meth:`fetchmany()` it is the default number of rows to fetch. The attribute is only used for tuning row and SODA document fetches from the database. It does not affect data inserts. Due to the performance benefits, the default ``arraysize`` is *100* instead of the *1* that the Python DB API recommends. )r(r arraysizer#s rrmzBaseCursor.arraysizes!( z##rvaluec|t|tr|dkrtjtj||j_dS)Nr)r( isinstanceintr rYERR_INVALID_ARRAYSIZErrmrrns rrmzBaseCursor.arraysizesR %%% <!  f: ; ; ;$ rrtypsizecd|t|trt|}n't|tr|}nt d|j|j|||d}t|tr| d||S)a Creates an array variable associated with the cursor of the given type and size and returns a :ref:`variable object `. The value is either an integer specifying the number of elements to allocate or it is a list and the number of elements allocated is drawn from the size of the list. If the value is a list, the variable is also set with the contents of the list. If the size is not specified and the type is a string or binary, 4000 bytes is allocated. This is needed for passing arrays to PL/SQL (in cases where the list might be empty and the type cannot be determined automatically) or returning arrays from PL/SQL. z#expecting integer or list of valuesT)ru num_elementsis_arrayr) r(rplistrPrq TypeErrorr create_varrsetvalue)rrtrnrurwvars rarrayvarzBaseCursor.arrayvars"  eT " " Cu::LL s # # C LLABB Bj## O % $   eT " " # LLE " " " rc||jjtjtj|jS)z Returns the list of bind variable names bound to the statement. Note that a statement must have been prepared first. )r(rr@r rYERR_NO_STATEMENT_PREPAREDget_bind_namesr#s r bindnameszBaseCursor.bindnamessI  :  '  f> ? ? ?z((***rc\||jS)a This read-only attribute provides the bind variables used for the last statement that was executed on the cursor. The value will be either a list or a dictionary, depending on whether binding was done by position or name. Care should be taken when referencing this attribute. In particular, elements should not be removed or replaced. )r(r get_bind_varsr#s rbindvarszBaseCursor.bindvarss* z'')))rcn||jd|_dS)z Closes the cursor now, rather than whenever ``__del__`` is called. The cursor will be unusable from this point forward; an Error exception will be raised if any operation is attempted with the cursor. Nr,r#s rr"zBaseCursor.close s5   rc||j|rd|jjDSdS)a> This read-only attribute contains information about the columns used in a query. It is a list of FetchInfo objects, one per column. This attribute will be *None* for statements that are not SELECT or WITH statements, or if the cursor has not had :meth:`execute()` invoked yet. c6g|]}tj|SrF)r _from_implrGs rrJz*BaseCursor.description..s#OOOI(++OOOrN)r(rrffetch_metadatar#s r descriptionzBaseCursor.descriptionsT  :  t $ $ POOTZ5NOOO O P Prc\||jS)a This read-only attribute specifies the list of variables created for the last SELECT query that was executed on the cursor. Care should be taken when referencing this attribute. In particular, elements should not be removed or replaced. )r(rget_fetch_varsr#s r fetchvarszBaseCursor.fetchvarss* z((***rc\||jS)a Retrieves the DML row counts after a call to :meth:`executemany()` with ``arraydmlrowcounts`` enabled. This will return a list of integers corresponding to the number of rows affected by the DML statement for each element of the array passed to :meth:`executemany()`. This method is only available for Oracle Database 12.1 and later. )r(rget_array_dml_row_countsr#s rgetarraydmlrowcountszBaseCursor.getarraydmlrowcounts*s* z22444rc\||jS)aG Retrieves the exceptions that took place after a call to :meth:`executemany()` with ``batcherrors`` enabled. This will return a list of Error objects, one error for each iteration that failed. The offset can be determined by looking at the offset attribute of the error object. )r(rget_batch_errorsr#s rgetbatcherrorszBaseCursor.getbatcherrors6s* z**,,,rch||j|jS)a Returns a list of cursors which correspond to implicit results made available from a PL/SQL block or procedure without the use of OUT ref cursor parameters. The PL/SQL block or procedure opens the cursors and marks them for return to the client using the procedure dbms_sql.return_result. In python-oracledb Thick mode, closing the parent cursor will result in the automatic closure of the implicit result set cursors. See :ref:`implicitresults`. This method is only available for Oracle Database 12.1 (or later). For python-oracledb :ref:`Thick ` mode, Oracle Client 12.1 (or later) is additionally required. )r(rget_implicit_resultsrr#s rgetimplicitresultszBaseCursor.getimplicitresultsAs. z..t???rcB||jjS)a/ This read-write attribute specifies a method called for each value that is bound to a statement executed on the cursor and overrides the attribute with the same name on the connection if specified. The method signature is handler(cursor, value, arraysize) and the return value is expected to be a variable object or *None* in which case a default variable object will be created. If this attribute is *None*, the default behavior will take place for all values bound to the statements. r(rinputtypehandlerr#s rrzBaseCursor.inputtypehandlerRs! z**rcF|||j_dSrrrss rrzBaseCursor.inputtypehandleras$ &+ ###rc\||jS)z This read-only attribute returns the rowid of the last row modified by the cursor. If no row was modified by the last operation performed on the cursor, the value *None* is returned. )r(r get_lastrowidr#s r lastrowidzBaseCursor.lastrowidfs* z'')))rcB||jjS)a This read-write attribute specifies a method called for each column that is to be fetched from this cursor. The method signature is handler(cursor, metadata) and the return value is expected to be a :ref:`variable object ` or *None* in which case a default variable object will be created. If this attribute is *None*, then the default behavior will take place for all columns fetched from this cursor. r(routputtypehandlerr#s rrzBaseCursor.outputtypehandlerps! z++rcF|||j_dSrrrss rrzBaseCursor.outputtypehandler~s$ ', $$$rcB||jjS)a+ This read-write attribute can be used to tune the number of rows that python-oracledb initially fetches from Oracle Database when a SELECT query is executed. The value can improve performance by reducing the number of round-trips to the database. The attribute does not affect data insertion. In python-oracledb Thin mode, prefetching can reuse the :attr:`arraysize` buffer. However in Thick mode, extra memory is required. Setting this value to *0* can be useful when the timing of fetches must be explicitly controlled. Queries that return :ref:`LOB ` objects and similar types do not support prefetching. The ``prefetchrows`` attribute is ignored in queries that involve these types. r(r prefetchrowsr#s rrzBaseCursor.prefetchrowss!( z&&rcF|||j_dSrrrss rrzBaseCursor.prefetchrowss$ "' rc\|||||dS)a This can be used before a call to :meth:`execute()` or :meth:`executemany()` to define the statement that will be executed. When this is done, the prepare phase will not be performed when the call to :meth:`execute()` or :meth:`executemany()` is made with *None* or the same string object as the statement. If the ``tag`` parameter is specified and the ``cache_statement`` parameter is *True*, the statement will be returned to the statement cache with the given tag. If the ``cache_statement`` parameter is *False*, the statement will be removed from the statement cache (if it was found there) or will simply not be cached. N)r(rbras rr`zBaseCursor.prepares2$  io66666rcD|j|jj |jjSdS)a This read-only attribute specifies the number of rows that have currently been fetched from the cursor (for select statements) or that have been affected by the operation (for insert, update, delete, and merge statements). For all other statements the value is always *0*. If the cursor or connection is closed, the value returned is *-1*. N)rrrowcountr#s rrzBaseCursor.rowcounts& : !do&;&G:& &rrcB||jjS)a This read-write attribute specifies a method to call for each row that is retrieved from the database. Ordinarily, a tuple is returned for each row but if this attribute is set, the method is called with the tuple that would normally be returned, and the result of the method is returned instead. The ``rowfactory`` attribute should be set after each statement execution before data is fetched from the cursor. r(r rowfactoryr#s rrzBaseCursor.rowfactorys! z$$rcF|||j_dSrrrss rrzBaseCursor.rowfactory$  % rcB||jjS)aq This read-write boolean attribute specifies whether the cursor can be scrolled or not. By default, cursors are not scrollable, as the server resources and response times are greater than nonscrollable cursors. This attribute is checked and the corresponding mode set in Oracle when calling the method :meth:`execute()`. r(rrr#s rrzBaseCursor.scrollables! z$$rcF|||j_dSrrrss rrzBaseCursor.scrollablerrargskwargsc|r!|rtjtjn9|s|r5||j|j||SgS)aM This can be used before calls to :meth:`execute()` or :meth:`executemany()` to predefine memory areas used for :ref:`bind variables `. Each parameter should be a type object corresponding to the data that will be used for a bind variable placeholder in the SQL or PL/SQL statement. Alternatively, it can be an integer specifying the maximum length of a string bind variable value. Use keyword parameters when :ref:`binding by name `. Use positional parameters when :ref:`binding by position `. The parameter value can be *None* to indicate that python-oracledb should determine the required space from the data value provided. The parameters or keyword names correspond to the bind variable placeholders used in the SQL or PL/SQL statement. Note this means that for use with :meth:`executemany()` it does not correspond to the number of bind value mappings or sequences being passed. When repeated calls to :meth:`execute()` or :meth:`executemany()` are made binding different string data lengths, using :meth:`setinputsizes()` can help reduce the database's SQL "version count" for the statement. See :ref:`Reducing the SQL Version Count `. )r rYERR_ARGS_AND_KEYWORD_ARGSr(r setinputsizesr)rrrs rrzBaseCursor.setinputsizessp2  KF K  f> ? ? ? ?  KV K      :++DOT6JJ J rcolumncdS)a This method does nothing and is retained solely for compatibility with the DB API. Python-oracledb automatically allocates as much space as needed to fetch LONG and LONG RAW columns, and also to fetch CLOB as string and BLOB as bytes. NrF)rrurs r setoutputsizezBaseCursor.setoutputsizes  rc,|j |jjSdS)z This read-only attribute provides the string object that was previously prepared with :meth:`prepare()` or executed with :meth:`execute()`. N)rr@r#s rr@zBaseCursor.statements : !:' ' " !rr)encodingErrorsrm inconverter outconvertertypenameencoding_errors bypass_decode convert_nullsrrc  P|||j|}n'|turt jtj| %|!t jtjdd| }|j |j||||||||  S)a6 Creates a :ref:`variable object ` with the specified characteristics. This method can be used for binding to PL/SQL IN and OUT parameters where the length or type cannot be determined automatically from the Python variable being bound. It can also be used in :ref:`input ` and :ref:`output ` type handlers. The ``typ`` parameter specifies the type of data that should be stored in the variable. This should be one of the :ref:`database type constants `, :ref:`DB API constants `, an object type returned from the method :meth:`Connection.gettype()` or one of the following Python types: - bool (uses :attr:`oracledb.DB_TYPE_BOOLEAN`) - bytes (uses :attr:`oracledb.DB_TYPE_RAW`) - datetime.date (uses :attr:`oracledb.DB_TYPE_DATE`) - datetime.datetime (uses :attr:`oracledb.DB_TYPE_DATE`) - datetime.timedelta (uses :attr:`oracledb.DB_TYPE_INTERVAL_DS`) - decimal.Decimal (uses :attr:`oracledb.DB_TYPE_NUMBER`) - float (uses :attr:`oracledb.DB_TYPE_NUMBER`) - int (uses :attr:`oracledb.DB_TYPE_NUMBER`) - str (uses :attr:`oracledb.DB_TYPE_VARCHAR`) The ``size`` parameter specifies the length of string and raw variables and is ignored in all other cases. If not specified for string and raw variables, the value *4000* is used. The ``arraysize`` parameter specifies the number of elements the variable will have. If not specified the bind array size (usually *1*) is used. When a variable is created in an output type handler this parameter should be set to the cursor's array size. The ``inconverter`` and ``outconverter`` parameters specify methods used for converting values to/from the database. More information can be found in the section on :ref:`variable objects`. The ``typename`` parameter specifies the name of a SQL object type and must be specified when using type :data:`oracledb.OBJECT` unless the type object was passed directly as the first parameter. The ``encoding_errors`` parameter specifies what should happen when decoding byte strings fetched from the database into strings. It should be one of the values noted in the builtin `decode `__ function. The ``bypass_decode`` parameter, if specified, should be passed as a boolean value. Passing a *True* value causes values of database types :data:`~oracledb.DB_TYPE_VARCHAR`, :data:`~oracledb.DB_TYPE_CHAR`, :data:`~oracledb.DB_TYPE_NVARCHAR`, :data:`~oracledb.DB_TYPE_NCHAR` and :data:`~oracledb.DB_TYPE_LONG` to be returned as bytes instead of str, meaning that python-oracledb does not do any decoding. See :ref:`Fetching raw data ` for more information. The ``convert_nulls`` parameter, if specified, should be passed as a boolean value. Passing the value *True* causes the ``outconverter`` to be called when a null value is fetched from the database; otherwise, the ``outconverter`` is only called when non-null values are fetched from the database. For consistency and compliance with the PEP 8 naming style, the parameter ``encodingErrors`` was renamed to ``encoding_errors``. The old name will continue to work as a keyword parameter for a period of time. Nrrdeprecated_namenew_name)r) r(rgettyper r rY$ERR_MISSING_TYPE_NAME_FOR_OBJECT_VARERR_DUPLICATED_PARAMETERrr{) rrtrurmrrrrrrrs rr}zBaseCursor.vars`   /))(33CC N " "  fI J J J  %*!3$4. -Oz$$ O       '%   rcB||jjS)a This read-only attribute provides an :ref:`oracledb._Error` object giving information about any database warnings (such as PL/SQL compilation warnings) that were generated during the last call to :meth:`execute()` or :meth:`executemany()`. This value is automatically cleared on the next call to :meth:`execute()` or :meth:`executemany()`. If no warning was generated the value *None* is returned. )r(rwarningr#s rrzBaseCursor.warnings! z!!r)Fr)NT)rNr)rrNNNNFF):__name__ __module__ __qualname__rboolrr$r)r0r7strrrytupledictrrBr>rr\rbrdrhr(propertyrqrmsetterr rtyperr~rrr"rrrrrrrrrrrr`rrrrrr@r}r _ErrorrrFrrrr,s E !EE2EE  EEEE***666! 444$+&4! 4  4  4444.! ((($+&(! (  (  ((((> hsm     HL<<<#&<@D< <<<<9=     6666,,,,$3$$$X$,%s%t%%%% !! 6<- .!T3Y! ! !!!!F+4++++ *$ * * *X * PU4 ?D#89 P P PX P+4+++X+ 5d 5 5 5 5 - - - - -@D@@@@" +( + + +X +,h,4,,,,*3***X* ,8 , , ,X ,-x-D----'c'''X',(#($(((( HL777#&7@D7 7777* #   X  %H % % %X %&&T&&&& %D % % %X %&&&&&&3#%d :K@  # s 4    (5d+(((X( $!%###g #g g g 6<- .g g  g  g  g g g g g g  g g g g R "v}d23 " " "X " " "rr) metaclassc8eZdZdZdZdededefdZdedededdfd Z d+dd d e d ed e e e e fde ede edef dZ d+dd d e d e e e e fde ede ede f dZed,dZ d-ddddde e d e e e e efdede ede ededefdZdddddde e d edededededdfd Zde fd!Z d+d"e ed#e ede fd$Zdefd%Zde ddfd&Zd.ded)e ddfd*ZdS)/Cursorc|S)zF Returns the cursor itself to be used as an iterator. rFr#s r__iter__zCursor.__iter__  rct||j|}||Str)rhrfetch_next_row StopIterationrrows r__next__zCursor.__next__s9 j''-- ?Jrattr_num attr_typerc`||j||S)z Returns the value of the specified OCI attribute from the internal handle. This is only supported in python-oracledb's thick mode and should only be used as directed by Oracle. )r(r _get_oci_attr)rrrs rrzCursor._get_oci_attrs. z'')<<` or an :ref:`Object Type `. The sequence of parameters must contain one entry for each parameter that the PL/SQL function expects. Any keyword parameters will be included after the positional parameters. Use :meth:`var()` to define any OUT or IN OUT parameters, if necessary. For consistency and compliance with the PEP 8 naming style, the parameter ``keywordParameters`` was renamed to ``keyword_parameters``. The old name will continue to work for a period of time. Nrr:r)r}r rYrrBgetvalue)rr8rr9r:rr}s rcallfunczCursor.callfuncsv4hh{##  (!-!3$71 "3  4%7===||~~rc|%|!tjtjdd|}|||||gSd|jjdt |DS)a Calls a PL/SQL procedure with the given name. The sequence of parameters must contain one entry for each parameter that the procedure expects. The result of the call is a modified copy of the input sequence. Input parameters are left untouched; output and input/output parameters are replaced with possibly new values. Keyword parameters will be included after the positional parameters and are not returned as part of the output sequence. Use :meth:`var()` to define any OUT or IN OUT parameters if necessary. No query result set is returned by this method. Instead, use :ref:`REF CURSOR ` parameters or :ref:`Implicit Results `. For consistency and compliance with the PEP 8 naming style, the parameter ``keywordParameters`` was renamed to ``keyword_parameters``. The old name will continue to work for a period of time. Nrr:rc8g|]}|dSr get_valuerHvs rrJz#Cursor.callproc../    AKKNN   r)r rYrrBr bind_varsrP)rr8r9r:rs rcallproczCursor.callprocs8  (!-!3$71 "3  4%7888  I  $(J$89J3z??9J$K    rrc|jSz This read-only attribute returns a reference to the connection object on which the cursor was created. rr#s rrzCursor.connection rFsuspend_on_success fetch_lobsfetch_decimalsr@rrrc |||||j}|||_|||_||_|||j|SdS)a Executes a statement against the database. See :ref:`sqlexecution`. Parameters may be passed as a dictionary or sequence or as keyword parameters. If the parameters are a dictionary, the values will be bound by name and if the parameters are a sequence the values will be bound by position. Note that if the values are bound by position, the order of the variables is from left to right as they are encountered in the statement and SQL statements are processed differently than PL/SQL statements. For this reason, it is generally recommended to bind parameters by name instead of by position. Parameters passed as a dictionary are name and value pairs. The name maps to the bind variable name used by the statement and the value maps to the Python value you wish bound to that bind variable. A reference to the statement will be retained by the cursor. If *None* or the same string object is passed in again, the cursor will execute that statement again without performing a prepare or rebinding and redefining. This is most effective for algorithms where the same statement is used, but different parameters are bound to it (many times). Note that parameters that are not passed in during subsequent executions will retain the value passed in during the last execution that contained them. The ``suspend_on_success`` parameter is specific to :ref:`sessionless transactions `. When set to *True*, the active sessionless transaction will be suspended when ``execute()`` completes successfully. See :ref:`suspendtxns`. The ``fetch_lobs`` parameter specifies whether to return LOB locators or ``str``/``bytes`` values when fetching LOB columns. The default value is :data:`oracledb.defaults.fetch_lobs `. The ``fetch_decimals`` parameter specifies whether to return ``decimal.Decimal`` values when fetching columns of type ``NUMBER``. The default value is :data:`oracledb.defaults.fetch_decimals `. For maximum efficiency when reusing a statement, it is best to use the :meth:`Cursor.setinputsizes()` method to specify the parameter types and sizes ahead of time; in particular, *None* is assumed to be a string of length 1 so any values that are later bound as numbers or dates will raise a TypeError exception. If the statement is a SELECT query, the cursor is returned as a convenience to the caller (so it can be used directly as an iterator over the rows in the cursor); otherwise, *None* is returned. N)rdrrrrr? fetch_varsrr@r9rrrr:impls rr?zCursor.execute sov !!)Z9KLLLz  !(DO  %"0D "4 T ? &K ' &r batcherrorsarraydmlrowcountsr batch_sizerrrcN||j|||||}||j_|jdkrI|j||j|||j||jdkGdSdS)a Executes a SQL statement once using all bind value mappings or sequences found in the sequence parameters. This can be used to insert, update, or delete multiple rows in a table with a single python-oracledb call. It can also invoke a PL/SQL procedure multiple times. See :ref:`batchstmnt`. The ``statement`` parameter is managed in the same way as the :meth:`execute()` method manages it. The ``parameters`` parameter can be a list of tuples, where each tuple item maps to one bind variable placeholder in ``statement``. It can also be a list of dictionaries, where the keys match the bind variable placeholder names in ``statement``. If there are no bind values, or values have previously been bound, the ``parameters`` value can be an integer specifying the number of iterations. The ``parameters`` parameter can also be a :ref:`DataFrame `, or a third-party data frame that supports the `Apache Arrow PyCapsule `__ Interface. In python-oracledb Thick mode, if the size of the buffers allocated for any of the parameters exceeds 2 GB, you will receive the error ``DPI-1015: array size of is too large``. If you receive this error, decrease the number of rows being inserted. When *True*, the ``batcherrors`` parameter enables batch error support within Oracle Database and ensures that the call succeeds even if an exception takes place in one or more of the sequence of bind values. The errors can then be retrieved using :meth:`getbatcherrors()`. When *True*, the ``arraydmlrowcounts`` parameter enables DML row counts to be retrieved from Oracle after the method has completed. The row counts can then be retrieved using :meth:`getarraydmlrowcounts()`. Both the ``batcherrors`` parameter and the ``arraydmlrowcounts`` parameter can only be *True* when executing an insert, update, delete, or merge statement; in all other cases an error will be raised. The ``suspend_on_success`` parameter is specific to :ref:`sessionless transactions `. When set to *True*, the active sessionless transaction will be suspended when ``executemany()`` completes successfully. See :ref:`suspendtxns`. The ``batch_size`` parameter is used to split large data sets into smaller pieces for sending to the database. It is the number of records in each batch. This parameter can be used to tune performance. When ``Connection.autocommit`` is *True*, a commit will take place for each batch. For maximum efficiency, it is best to use the :meth:`setinputsizes()` method to specify the bind value types and sizes. In particular, if the type is not explicitly specified, the value *None* is assumed to be a string of length 1 so any values that are later bound as numbers or dates will raise a TypeError exception. rN r(r_prepare_for_executemanyr\rnum_rows executemanymessage_offset next_batchrr@r9rrrrmanagers rr zCursor.executemanyPsF *55   % %i 0 0      ); %"" J " " !&        """"""rc|g}|jj} ||}|n||$|S)a Fetches all (remaining) rows of a SELECT query result, returning them as a list of tuples. An empty list is returned if no more rows are available. An exception is raised if the previous call to :meth:`execute()` did not produce any result set or no call was issued yet. Note that the cursor's :attr:`~Cursor.arraysize` attribute can affect the performance of this operation, as internally data is fetched in batches of that size from the database. See :ref:`Tuning Fetch Performance `. An exception is raised if the previous call to :meth:`execute()` did not produce any result set or no call was issued yet. rhrrrMrresultrrs rfetchallzCursor.fetchalls_ 2  .&&C{ MM#       rrunumRowscJ||||}n0|jj}n#|!tjtjddg}|jj}t||kr6||}|n(||t||k6|S)a Fetches the next set of rows of a SELECT query result, returning a list of tuples. An empty list is returned if no more rows are available. Note that the cursor's :attr:`arraysize` attribute can affect the performance of this operation. The number of rows to fetch is specified by the ``size`` parameter. If it is not given, the cursor's :attr:`arraysize` attribute determines the number of rows to be fetched. If the number of rows available to be fetched is fewer than the amount requested, fewer rows will be returned. An exception is raised if the previous call to :meth:`execute()` did not produce any result set or no call was issued yet. Nrrur) rhrrmr rYrrrPrM)rrurrrrs r fetchmanyzCursor.fetchmanys$  <"z+   / )     2&kkD   .&&C{ MM#    &kkD   rc^||j|S) Fetches the next row of a SELECT query result set, returning a single tuple or *None* when no more data is available. An exception is raised if the previous call to :meth:`execute()` did not produce any result set or no call was issued yet. When ``fetchone()`` is used to iterate over a result set, the cursor’s :attr:`arraysize` attribute can affect performance, as internally data is fetched in batches of that size from Oracle Database. rhrrr#s rfetchonezCursor.fetchones, z((...rc||||j|dSz This can be used to parse a statement without actually executing it (parsing step is done automatically by Oracle when a statement is :meth:`executed `). Nr(rbrparser[s rr!z Cursor.parsesD  i    rrrelativemodec||jjstjtj|j|||dSah Scrolls the cursor in the result set to a new position according to the mode. If mode is *relative* (the default value), the value is taken as an offset to the current position in the result set. If set to *absolute*, value states an absolute target position. If set to *first*, the cursor is positioned at the first row and if set to *last*, the cursor is set to the last row in the result set. An error is raised if the mode is *relative* or *absolute* and the scroll operation would position the cursor outside of the result set. Nr(rrr rYERR_SCROLL_NOT_SUPPORTEDscrollrrnr#s rr(z Cursor.scrollsW z$ ?  f= > > > $t,,,,,rNN)rrrrr")rrrrrrqrrrrrrryrrrrrrrr?r rrrr!r(rFrrrrs =c=c=c=====c=c=#=$====48-1 $-1$$$$$U4;/0 $ %TN $$D>$ $$$$R48-1 ) -1 ) ) ) ) U4;/0) %TN ) $D> )  ) ) ) ) V   X :>D $)%))-DDDC=DU4#456D ! D TN D!D"D DDDDV""'#(#S!S!S!C=S!S!  S!  S!!S!S! S!S!S!S!j$6DH%%SM%3;C=% %%%%N /# / / / /st--C-3-------rrceZdZdZdZdZdZ d&dedede e e e fd e e d ef d Z d&dede e e e fd e e d e fd Zed'dZ d(ddddde ede e e e e fdede ede ed ed dfdZdddddde edededededed dfdZd e fdZd(de ed e fdZd efdZded dfd Zd)d#ed$ed dfd%ZdS)* AsyncCursorc2K||Sr&r'r#s r __aenter__zAsyncCursor.__aenter__s  rcvK||jdd|_dSr+r,)rexc_infos r __aexit__zAsyncCursor.__aexit__s>  %%% rc|S)zS Returns the cursor itself to be used as an asynchronous iterator. rFr#s r __aiter__zAsyncCursor.__aiter__$rrcK||j|d{V}||Str)rhrrStopAsyncIterationrs r __anext__zAsyncCursor.__anext__*sO J--d33333333 ?J  rNr8rr9r:rcK||}|||||d{V|S)a Calls a PL/SQL function with the given name and returns its value. The ``return_type`` parameter is expected to be a Python type, one of the :ref:`oracledb types ` or an :ref:`Object Type `. The sequence of parameters must contain one entry for each parameter that the PL/SQL function expects. Any keyword parameters will be included after the positional parameters. Use :meth:`var()` to define any OUT or IN OUT parameters, if necessary. N)r}rBr)rr8rr9r:r}s rrzAsyncCursor.callfunc1sR(hh{##jjz+=sCCCCCCCCC||~~rcK||||d{V|gSd|jjdt|DS)a Calls a PL/SQL procedure with the given name. The sequence of parameters must contain one entry for each parameter that the procedure expects. The result of the call is a modified copy of the input sequence. Input parameters are left untouched; output and input/output parameters are replaced with possibly new values. Keyword parameters will be included after the positional parameters and are not returned as part of the output sequence. Use :meth:`var()` to define any OUT or IN OUT parameters if necessary. No query result set is returned by :meth:`callproc()`. Instead, use :ref:`REF CURSOR ` parameters or :ref:`Implicit Results `. Nc8g|]}|dSrrrs rrJz(AsyncCursor.callproc..brr)rBrrrP)rr8r9r:s rrzAsyncCursor.callprocIss,jjz+=>>>>>>>>>  I  $(J$89J3z??9J$K    r!connection_module.AsyncConnectionc|jSrrr#s rrzAsyncCursor.connectionfrrFrr@rrrcK|||||j}||_|||_|||_|j|d{VdS)a Executes a statement against the database. See :ref:`sqlexecution`. Parameters may be passed as a dictionary or sequence or as keyword parameters. If the parameters are a dictionary, the values will be bound by name and if the parameters are a sequence the values will be bound by position. Note that if the values are bound by position, the order of the variables is from left to right as they are encountered in the statement and SQL statements are processed differently than PL/SQL statements. For this reason, it is generally recommended to bind parameters by name instead of by position. Parameters passed as a dictionary are name and value pairs. The name maps to the bind variable name used by the statement and the value maps to the Python value you wish bound to that bind variable. A reference to the statement will be retained by the cursor. If *None* or the same string object is passed in again, the cursor will execute that statement again without performing a prepare or rebinding and redefining. This is most effective for algorithms where the same statement is used, but different parameters are bound to it (many times). Note that parameters that are not passed in during subsequent executions will retain the value passed in during the last execution that contained them. The ``suspend_on_success`` parameter is specific to :ref:`sessionless transactions `. When set to *True*, the active sessionless transaction will be suspended when ``execute()`` completes successfully. See :ref:`suspendtxns`. The ``fetch_lobs`` parameter specifies whether to return LOB locators or ``str``/``bytes`` values when fetching LOB columns. The default value is :data:`oracledb.defaults.fetch_lobs `. The ``fetch_decimals`` parameter specifies whether to return ``decimal.Decimal`` values when fetching columns of type ``NUMBER``. The default value is :data:`oracledb.defaults.fetch_decimals `. For maximum efficiency when reusing a statement, it is best to use the :meth:`setinputsizes()` method to specify the parameter types and sizes ahead of time; in particular, *None* is assumed to be a string of length 1 so any values that are later bound as numbers or dates will raise a TypeError exception. If the statement is a SELECT query, the cursor is returned as a convenience to the caller (so it can be used directly as an iterator over the rows in the cursor); otherwise, *None* is returned. N)rdrrrrr?rs rr?zAsyncCursor.executenszv !!)Z9KLLLz"4  !(DO  %"0D j  &&&&&&&&&&&rrrrrrc^K||j|||||}||j_|jdkrO|j||j|||jd{V||jdkMdSdS)a Executes a SQL statement once using all bind value mappings or sequences found in the sequence parameters. This can be used to insert, update, or delete multiple rows in a table with a single python-oracledb call. It can also invoke a PL/SQL procedure multiple times. See :ref:`batchstmnt`. The ``statement`` parameter is managed in the same way as the :meth:`execute()` method manages it. The ``parameters`` parameter can be a list of tuples, where each tuple item maps to one bind variable placeholder in ``statement``. It can also be a list of dictionaries, where the keys match the bind variable placeholder names in ``statement``. If there are no bind values, or values have previously been bound, the ``parameters`` value can be an integer specifying the number of iterations. The ``parameters`` parameter can also be a :ref:`DataFrame `, or a third-party data frame that supports the `Apache Arrow PyCapsule `__ Interface. In python-oracledb Thick mode, if the size of the buffers allocated for any of the parameters exceeds 2 GB, you will receive the error ``DPI-1015: array size of is too large``. If you receive this error, decrease the number of rows being inserted. When True, the ``batcherrors`` parameter enables batch error support within Oracle and ensures that the call succeeds even if an exception takes place in one or more of the sequence of parameters. The errors can then be retrieved using :meth:`getbatcherrors()`. When True, the ``arraydmlrowcounts`` parameter enables DML row counts to be retrieved from Oracle after the method has completed. The row counts can then be retrieved using :meth:`getarraydmlrowcounts()`. Both the ``batcherrors`` parameter and the ``arraydmlrowcounts`` parameter can only be True when executing an insert, update, delete, or merge statement. In all other cases, an error will be raised. The ``suspend_on_success`` parameter is specific to :ref:`sessionless transactions `. When set to *True*, the active sessionless transaction will be suspended when ``executemany()`` completes successfully. See :ref:`suspendtxns`. The ``batch_size`` parameter is used to split large data sets into smaller pieces for sending to the database. It is the number of records in each batch. This parameter can be used to tune performance. When ``Connection.autocommit`` is *True*, a commit will take place for each batch. Do not set ``batch_size`` when ``suspend_on_success`` is *True*. For maximum efficiency, it is best to use the :meth:`setinputsizes()` method to specify the parameter types and sizes ahead of time. In particular, the value *None* is assumed to be a string of length 1 so any values that are later bound as numbers or dates will raise a TypeError exception. rNr rs rr zAsyncCursor.executemanysD *55 $++I66 J  ); %""*(( !&            """"""rcK|g}|jj} ||d{V}|n||*|S)a Fetches all (remaining) rows of a SELECT query result, returning them as a list of tuples. An empty list is returned if no more rows are available. An exception is raised if the previous call to :meth:`execute()` did not produce any result set or no call was issued yet. Note that the cursor's :attr:`~AsyncCursor.arraysize` attribute can affect the performance of this operation, as internally data is fetched in batches of that size from the database. TNrrs rrzAsyncCursor.fetchallsu 2 &t,,,,,,,,C{ MM#       rrucK|| |jj}g}|jj}t ||kr<||d{V}|n(||t ||k<|S)a Fetches the next set of rows of a SELECT query result, returning a list of tuples. An empty list is returned if no more rows are available. Note that the cursor's :attr:`arraysize` attribute can affect the performance of this operation. The number of rows to fetch is specified by the parameter. If it is not given, the cursor's :attr:`arraysize` attribute determines the number of rows to be fetched. If the number of rows available to be fetched is fewer than the amount requested, fewer rows will be returned. An exception is raised if the previous call to :meth:`execute()` did not produce any result set or no call was issued yet. N)rhrrmrrPrM)rrurrrs rrzAsyncCursor.fetchmanys  <:'D2&kkD  &t,,,,,,,,C{ MM#    &kkD   rcnK||j|d{VS)rNrr#s rrzAsyncCursor.fetchone4sB Z..t444444444rcK||||j|d{VdSrr r[s rr!zAsyncCursor.parseBsZ  i   jt$$$$$$$$$$$rrr"rnr#cK||jjstjtj|j|||d{VdSr%r&r)s rr(zAsyncCursor.scrollLsm z$ ?  f= > > >jeT22222222222rr*)rr;rr+)rrrr/r2r4r7rrrrryrrrrrrrr?rqr rrrr!r(rFrrr-r-s !!!48-1 U4;/0  %TN  648-1    U4;/0 %TN       :   X :>B' $)%))-B'B'B'C=B'U4#456B' ! B' TN B'!B'"B' B'B'B'B'R""'#(#O!O!O!C=O!O!  O!  O!!O!O! O!O!O!O!b,HSMT6 5 5 5 5 5%S%T%%%%33#33d333333rr-N)typingrrrrrLrconnection_moduler r baser base_implr r dbobjectr fetch_inforr}rrrr-rFrrrJsl@211111111111--------------""""""!!!!!!a "a "a "a "a "=a "a "a "a "H-----Z---D K3K3K3K3K3*K3K3K3K3K3r