If an edition is set that is not valid in the database, connection
will fail even if oci_set_edition() returns success.

When using persistent connections, if a connection with the
requested edition setting already exists, it is reused. Otherwise,
a different persistent connection is created

Parameters

edition

Oracle Database edition name previously created with the SQL
"CREATE EDITION" command.

Notes

Note:
Oracle version requirement

This function is available from Oracle 11gR2 onwards.

Caution

Persistent connections

To avoid inconsistencies and unexpected errors, do not use ALTER
SESSION SET EDITION to change the edition on persistent connections.

Caution

DRCP Connection Pooling

To avoid inconsistencies and unexpected errors when using editions
and DRCP with Oracle
11.2.0.1, keep a one-to-one correspondence between
the oci8.connection_class
and the edition name used by applications. Each pooled server of
a given connection class should only be used with one edition.
This restriction has been removed with Oracle 11.2.0.2.

Return Values

Returns TRUE on success or FALSE on failure.

Examples

Example #1 Two scripts can use different versions of myfunc() at the same time