@@ -422,38 +422,34 @@ or eliminating down time. This feature allows multiple versions of views,
422422synonyms, PL/SQL objects and SQL Translation profiles to be used concurrently.
423423Different versions of the database objects are associated with an "edition".
424424
425- .. note ::
426-
427- Setting the Edition-Based Redefinition (EBR) edition at connection time is
428- only supported in the python-oracledb Thick mode. See
429- :ref: `enablingthick `. In python-oracledb Thin mode, the edition can be
430- changed with ALTER SESSION after connecting.
431-
432- The simplest way to set an edition is to pass the ``edition `` parameter to
433- :meth: `oracledb.connect() ` or :meth: `oracledb.create_pool() `:
425+ The simplest way to set the edition used by your applications is to pass the
426+ ``edition `` parameter to :meth: `oracledb.connect() ` or
427+ :meth: `oracledb.create_pool() `:
434428
435429.. code-block :: python
436430
437431 connection = oracledb.connect(user = " hr" , password = userpwd,
438432 dsn = " dbhost.example.com/orclpdb" ,
439- edition = " newsales" , encoding = " UTF-8 " )
433+ edition = " newsales" )
440434
441435
442- The edition could also be set by setting the environment variable
443- ``ORA_EDITION `` or by executing the SQL statement:
436+ The edition can also be set by executing the SQL statement:
444437
445438.. code-block :: sql
446439
447440 alter session set edition = <edition name>;
448441
449- Regardless of which method is used to set the edition, the value that is in use
450- can be seen by examining the attribute :attr: `Connection.edition `. If no value
451- has been set, the value will be None. This corresponds to the database default
442+ You can also set the environment variable ``ORA_EDITION `` to your edition name.
443+
444+ Regardless of which method sets the edition, the value that is in use can be
445+ seen by examining the attribute :attr: `Connection.edition `. If no value has
446+ been set, the value will be None. This corresponds to the database default
452447edition ``ORA$BASE ``.
453448
454449Consider an example where one version of a PL/SQL function ``Discount `` is
455450defined in the database default edition ``ORA$BASE `` and the other version of
456- the same function is defined in a user created edition ``DEMO ``.
451+ the same function is defined in a user created edition ``DEMO ``. In your SQL
452+ editor run:
457453
458454.. code-block :: sql
459455
@@ -494,14 +490,13 @@ The ``Discount`` function for the demo edition is as follows:
494490 END;
495491 /
496492
497- The Python application can then call the required version of the PL/SQL
498- function as shown:
493+ A Python application can then call the required version of the PL/SQL function
494+ as shown:
499495
500496.. code-block :: python
501497
502498 connection = oracledb.connect(user = user, password = password,
503- dsn = " dbhost.example.com/orclpdb" ,
504- encoding = " UTF-8" )
499+ dsn = " dbhost.example.com/orclpdb" )
505500 print (" Edition is:" , repr (connection.edition))
506501
507502 cursor = connection.cursor()
@@ -511,7 +506,7 @@ function as shown:
511506 # Use the edition parameter for the connection
512507 connection = oracledb.connect(user = user, password = password,
513508 dsn = " dbhost.example.com/orclpdb" ,
514- edition = " demo" , encoding = " UTF-8 " )
509+ edition = " demo" )
515510 print (" Edition is:" , repr (connection.edition))
516511
517512 cursor = connection.cursor()
0 commit comments