Crate oci_rs[][src]

This crate provides a Rust wrapper to the Oracle Call Interface (OCI) library. The Oracle site describes OCI as a "...comprehensive, high performance, native C language interface to Oracle Database for custom or packaged applications...".


The OCI library is the original Oracle C API for interacting with their database. It is one of the driver options available in JDBC. Recently Oracle released a new API called the Oracle Database Programming Interface for Drivers and Applications (ODPI-C) that is supposed to simplify use of OCI, however the documentation for OCI is more extensive and therefore easier to build a wrapper on top of.

The OCI library is large and supports many use cases for interacting with a database. This crate is currently concerned with support for executing SQL statements and so is limited when compared to the whole of OCI.

The overall design will be familiar to anyone who has used Java's JDBC, Haskell's HDBC or Rust's postgres crate. Indeed, most design decisions were made based on reviewing the API of these libraries.

The basics are simple: a Connection represents a connection to a database, this connection can be used to prepare one or more Statements which are then used to execute SQL against the database. If there are results then they can be returned all at once or lazily via an iterator. Datatypes are represented using SqlValue and allow type conversion from Oracle to Rust types.

Missing type conversions

The following conversions are supported to/from Oracle SQL types to Rust types. As Oracle uses NUMBER to represent all number types then all integer and floating point types convert to it. Smaller integers or floats needed on the Rust side can be downcast.

Oracle SQL type Rust type
CHAR String
NUMBER i64, f64
DATE Date<Utc>

Over time more types will be added.


This crate is developed against version 12.2 of the OCI library. It is expected to work with 12.x.x but is not tested. The OCI client library needs to be installed on your machine and can be downloaded here.

If you are on Linux then you are likely to need to tell the linker where to find the files. Adding this to my .bashrc file worked for me, however the details may vary according to your distro. The below works on OpenSuse.

export LIBRARY_PATH=$LIBRARY_PATH:/usr/lib/oracle/12.2/client64/lib/

You can build this crate on Windows hosts using the windows-gnu toolchain. The only requirement for this is that oci.dll is on the PATH.

This crate has been briefly tested against Windows but difficulties were faced. The OCI library is named differently and so updates will be needed in the bindings to make it compile. Once I can get chance to work out how to even build this using Visual Studio on Windows, this will be addressed.

Testing has been done against a local installation of Oracle 11g Express Edition. In order to run the crate tests then a local database needs to be available on localhost:1521/xe with a user oci_rs and password test.

Note that users of Debian based systems will face a lot of bother using Oracle databases locally. It does not install easily due to lack of official packages and the use of Alien will not help much. There are lots of complicated instructions available on the internet for how to get it to work, however the easiest is to run it in a [Docker container][13]. I have switched to [Ubuntu][12] and have had to resort to using Docker.

In order to use oci_rs add this to your Cargo.toml:

oci_rs = "0.8.0"

and this to your crate root:

extern crate oci_rs;


In the following example we will create a connection to a database and then create a table, insert a couple of rows using bind variables and then execute a query to fetch them back again. There is a lot of error handling needed. Every OCI function call can fail and so Result and Option are used extensively. The below code takes the usual documentation shortcut of calling unwrap() a lot but doing so in real client code will prove ill-fated. Any remote database connection is inherently unreliable.

use oci_rs::connection::Connection;

let conn = Connection::new("localhost:1521/xe", "oci_rs", "test").unwrap();

// Create a table
let sql_create = "CREATE TABLE Toys (ToyId int,
                                     Name varchar(20),
                                     Price float)";
let mut create = conn.create_prepared_statement(sql_create).unwrap();

// Execute the create statement

// Commit in case we lose connection (an abnormal disconnection would result
// in an automatic roll-back.)

// Insert some values using bind variables
let sql_insert = "INSERT INTO Toys (ToyId, Name, Price)
                  VALUES (:id, :name, :price)";
let mut insert = conn.create_prepared_statement(sql_insert).unwrap();

let values = [(1, "Barbie", 23.45),
              (2, "Dinosaurs", -5.21)];

// Run through the list of values, bind them and execute the statement
for value in values.iter() {
    insert.bind(&[&value.0, &value.1, &value.2]).unwrap();


// Create a query
let sql_select = "SELECT * FROM Toys
                  WHERE Name='Barbie'";

let mut select = conn.create_prepared_statement(sql_select).unwrap();

// Execute

// Get the result set
let result_set = select.result_set().unwrap();
assert_eq!(result_set.len(), 1);
let first_row = &result_set[0];

// Types are automatically converted
let id: i64 = first_row[0].value().unwrap();
let name: String = first_row[1].value().unwrap();
let price: f64 = first_row[2].value().unwrap();

assert_eq!(id, 1);
assert_eq!(name, "Barbie");
assert_eq!(price, 23.45);

OCI docs

Documentation for the underlying OCI library can be found [here][10] and error codes and their descriptions [here][11]. The error descriptions are useful because they often contain additional information that is not included in the text returned from the library.

overview/index.html [10]: [11]: [12]: [13]:



Connections to a database.




Rows of data returned from a query


SQL statements run against the database.


Types used in conversion between OCI and Rust types.