K
KUBO Takehiro
ruby-oci8 1.0.0-rc1 is released. This is a Oracle module using OCI8 API.
If this works fine on environments described later, it will be 1.0.0.
http://rubyforge.org/projects/ruby-oci8/
I have been reported several times that 0.1.16 had not work but 0.1.15 is
OK. But both work fine on my environments even though on the reported
OS and Oracle client version. If this works fine on such environments,
please report me.
The differnce between 0.1.15 and 0.1.16 which may be related to the
problem is the API to initialize the OCI environment. The former uses
OCIInitialize() and OCIEnvInit(). The latter uses OCIEnvCreate().
OCIEnvCreate() is a new API in Oracle 8.1, which is the recommended
API by Oracle. OCIInitialize() and OCIEnvInit() are both available for
backward compatibility.
I prefer to use the recommended API. But I found that if environment
variable ORACLE_HOME ends with '/' on UNIX or '\' on Windows, 0.1.16
raises OCIError but 0.1.15 has no problem. So 1.0.0-rc1 uses the
0.1.15's way to initialize the OCI environment.
If this works fine on environments described later, it will be 1.0.0.
http://rubyforge.org/projects/ruby-oci8/
I have been reported several times that 0.1.16 had not work but 0.1.15 is
OK. But both work fine on my environments even though on the reported
OS and Oracle client version. If this works fine on such environments,
please report me.
The differnce between 0.1.15 and 0.1.16 which may be related to the
problem is the API to initialize the OCI environment. The former uses
OCIInitialize() and OCIEnvInit(). The latter uses OCIEnvCreate().
OCIEnvCreate() is a new API in Oracle 8.1, which is the recommended
API by Oracle. OCIInitialize() and OCIEnvInit() are both available for
backward compatibility.
I prefer to use the recommended API. But I found that if environment
variable ORACLE_HOME ends with '/' on UNIX or '\' on Windows, 0.1.16
raises OCIError but 0.1.15 has no problem. So 1.0.0-rc1 uses the
0.1.15's way to initialize the OCI environment.